From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1665 invoked by alias); 8 Jun 2004 14:57:06 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 15231 invoked by uid 48); 8 Jun 2004 14:38:14 -0000 Date: Tue, 08 Jun 2004 14:57:00 -0000 Message-ID: <20040608143814.15230.qmail@sourceware.org> From: "jakub at redhat dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20040607084537.207.a.darovskikh@compassplus.ru> References: <20040607084537.207.a.darovskikh@compassplus.ru> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/207] ucontext is very slow. X-Bugzilla-Reason: CC X-SW-Source: 2004-06/txt/msg00030.txt.bz2 List-Id: ------- Additional Comments From jakub at redhat dot com 2004-06-08 14:38 ------- Hardly. More than 50% of the time is spent in sigprocmask syscalls, which are needed (the program can change its signal mask any time and this needs to be preserved, caching current signal mask in userland would be a huge can of problems and slowdowns for little gain). The other big part of the total time is spent on saving/restoring FPU state (again, swapcontext must do this) and that's about it. Why aren't you using real threads instead? -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://sources.redhat.com/bugzilla/show_bug.cgi?id=207 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.