public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "a dot darovskikh at compassplus dot ru" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/207] New: ucontext is very slow.
Date: Mon, 07 Jun 2004 08:45:00 -0000	[thread overview]
Message-ID: <20040607084537.207.a.darovskikh@compassplus.ru> (raw)

We use ucontext related functions in our project.
We port it from Windows, where we used to deal with
*Fiber functions. During the tests we discovered that
our task engine on linux is near 10 times slower than 
windows one.

Here are two small examples on context swapping on windows fibers
and unix ucontexts. Unix one works near 5 seconds against 0.4 on
windows one.

Is it possible to improve perfomance?

Thanks in advance. Alexander Darovsky.

-- 
           Summary: ucontext is very slow.
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: a dot darovskikh at compassplus dot ru
                CC: glibc-bugs at sources dot redhat dot com
  GCC host triplet: Linux 2.6.0


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.


             reply	other threads:[~2004-06-07  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07  8:45 a dot darovskikh at compassplus dot ru [this message]
2004-06-07  8:47 ` [Bug libc/207] " a dot darovskikh at compassplus dot ru
2004-06-07  8:48 ` a dot darovskikh at compassplus dot ru
2004-06-08 14:57 ` jakub at redhat dot com
2004-06-09  4:31 ` a dot darovskikh at compassplus dot ru
2004-08-10  2:06 ` drepper at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040607084537.207.a.darovskikh@compassplus.ru \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).