From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] epoll bits 0.30 ...
Date: Fri, 8 Nov 2002 16:09:55 +0000 [thread overview]
Message-ID: <20021108160955.GA30234@bjl1.asuk.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0211061641180.953-100000@blue1.dev.mcafeelabs.com>
Davide Libenzi wrote:
> Rusty, the hash is not under pressure over there. The only time seeks is
> performed is at file removal ( from the set ) and eventually at file
> modify. There's a direct link between the wait queue and its item during
> the high frequency event delivery, so need seek is performed.
It does seem peculiar to use a prime-sized hash table, though. These
days, good power-of-two-sized hash functions are well known.
-- Jamie
next prev parent reply other threads:[~2002-11-08 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 3:44 Davide Libenzi
2002-11-06 1:46 ` Rusty Russell
2002-11-07 0:46 ` Davide Libenzi
2002-11-07 1:00 ` Davide Libenzi
2002-11-08 16:09 ` Jamie Lokier [this message]
2002-11-08 17:37 ` Davide Libenzi
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=20021108160955.GA30234@bjl1.asuk.net \
--to=lk@tantalophile.demon.co.uk \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®