From: Davide Libenzi <davidel@xmailserver.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Changli Gao <xiaosuo@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Improve scalability of epoll_ctl
Date: Tue, 8 Jan 2008 12:30:58 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0801081226090.7616@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <4783A41B.1090100@cosmosbay.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1337 bytes --]
On Tue, 8 Jan 2008, Eric Dumazet wrote:
> Changli Gao a écrit :
> > Replace the epitem rbtree with a dynamic array to get the constant insertion/deletion/modification time of the file descriptors. Reuse the size argument of epoll_create, however the size must be smaller than the max file descriptor number: ether the resource limitation or the compiling time limitation.
> >
> >
> Hum, you should read this :
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/2.6.7-rc3-mm2/broken-out/epoll-uses-rbtrees.patch
>
>
> Your patch is a revert of this change, it probably wont be accepted.
>
> epoll_ctl() is scalable, since it's O(log2(N)) : With 1 millions files
> descriptors, that means less than 20 nodes to lookup in the tree.
Indeed, and we aren't going back.
> In what situation do you think epoll_ctl() performance is bad ?
I'm sure you can cook up a microbench that only does epoll_ctl(), and with
a good hash implementation you get better numbers. This is what I did
before I changed to rbtree, and the numbers did not justify the code (the
"size" in epoll_create() is just an hint, and that means you need to
handle resizing - plus other things like locking up memory when the number
of fds shrinks, and other stuff I don't even remember).
- Davide
next prev parent reply other threads:[~2008-01-08 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 15:34 Changli Gao
2008-01-08 16:26 ` Eric Dumazet
2008-01-08 20:30 ` Davide Libenzi [this message]
2008-01-08 16:56 ` Andi Kleen
2008-01-09 1:20 ` Changli Gao
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=Pine.LNX.4.64.0801081226090.7616@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaosuo@gmail.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®