From: William Josephson <jkw@eecs.harvard.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] notify woe
Date: Tue, 6 Apr 2004 23:28:55 -0400 [thread overview]
Message-ID: <20040407032855.GA31468@mero.morphisms.net> (raw)
In-Reply-To: <019f01c41c47$c8385fd0$8201a8c0@cc77109e>
On Wed, Apr 07, 2004 at 12:16:04PM +1000, Bruce Ellis wrote:
> i believe this bug to be simply that a (in this case single threaded)
> program is interrupted holding the malloc pool lock. the notify
> function indirectly calls malloc. sleep time.
Yep; that's the one (though I hit it somewhere inside
the thread scheduler and there's now a hack to mitigate
that particular instance).
prev parent reply other threads:[~2004-04-07 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 1:10 Bruce Ellis
2004-04-07 1:40 ` William Josephson
2004-04-07 2:16 ` Bruce Ellis
2004-04-07 3:28 ` William Josephson [this message]
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=20040407032855.GA31468@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).