From: Marko Macek <Marko.Macek@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: Simon Kirby <sim@stormix.com>
Subject: Re: kqueue microbenchmark resul
Date: Sat, 28 Oct 2000 08:21:06 +0200 [thread overview]
Message-ID: <39FA7052.9C11541@gmx.net> (raw)
>In fact, if you did leave the read queued in a daemon using select()
>before, you'd keep looping endlessly taking all CPU and never idle
>because there would always be read data available.
Also, level triggered notifications would also seem to cause
multiple thread wakeups and thundering herd problems when
there are multiple worker threads reading from the same queue.
How does (?) kevent avoid this from happening?
Mark
--
... recursive make suxx!
------------------------------------------------------------------------
Marko.Macek@gmx.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-10-28 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-28 6:21 Marko Macek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-28 23:51 kqueue microbenchmark resul Dan Kegel
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=39FA7052.9C11541@gmx.net \
--to=marko.macek@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@stormix.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