From: Davide Libenzi <davidel@xmailserver.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Avi Kivity <avi@argo.co.il>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [patch] epoll use a single inode ...
Date: Tue, 6 Mar 2007 17:47:33 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703061745580.3661@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703061721110.5963@woody.linux-foundation.org>
On Tue, 6 Mar 2007, Linus Torvalds wrote:
>
>
> On Tue, 6 Mar 2007, Davide Libenzi wrote:
> >
> > I'm OK with everything that avoid code duplication due to those fake
> > inodes. The change can be localized inside the existing API, so it doesn't
> > really affect me externally.
>
> Can you try with the first patch version that doesn't do anything special
> at all, and just uses a single dentry.
>
> Yeah, the dentry name will be identical, and so you would see something
> like "7 -> signalfd:signalfd" when you do "ls -l /proc/<pid>/fd/" on a
> task that has such a special file descriptor (with no way to tell
> different timerfd's and signalfd's apart), but I think it's better to
> start off simple than to overdesign things.
>
> And trying to tell them apart sounds a bit like overdesign, if only
> because I really don't see why anybody would really *care*. So it's a
> timer for poll/select/epoll - why care about anything else?
The code would not change/shrink much with the single dentry. We'd save
memory, and we'd lose the capability of seeing aino:[CLASS].
Both ways are fine with me.
- Davide
next prev parent reply other threads:[~2007-03-07 1:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45ED1A3C.6030707@argo.co.il>
2007-03-07 0:37 ` Davide Libenzi
2007-03-07 0:51 ` Linus Torvalds
2007-03-07 1:01 ` Davide Libenzi
2007-03-07 1:27 ` Linus Torvalds
2007-03-07 1:47 ` Davide Libenzi [this message]
2007-03-07 6:52 ` Eric Dumazet
2007-03-07 7:15 ` Davide Libenzi
2007-03-07 7:16 ` Eric Dumazet
2007-03-07 8:56 ` Christoph Hellwig
2007-03-07 17:21 ` Linus Torvalds
2007-03-07 17:02 ` Linus Torvalds
2007-03-07 17:31 ` Eric Dumazet
2007-03-07 17:36 ` Eric Dumazet
2007-03-07 17:45 ` Linus Torvalds
2007-03-07 18:06 ` Eric Dumazet
2007-03-07 18:30 ` Linus Torvalds
2007-03-07 18:52 ` Eric Dumazet
2007-03-07 19:07 ` Linus Torvalds
2007-03-07 22:14 ` Anton Blanchard
2007-03-07 22:57 ` Linus Torvalds
2007-03-08 1:25 ` Michael K. Edwards
2007-03-08 2:48 ` Kyle Moffett
2007-03-08 7:24 ` Eric Dumazet
2007-03-08 16:57 ` Valdis.Kletnieks
2007-03-09 1:34 ` Kyle Moffett
2007-03-09 2:52 ` Anton Blanchard
2007-03-09 2:51 ` Anton Blanchard
2007-03-08 3:20 ` Linus Torvalds
2007-03-08 8:37 ` Michael K. Edwards
2007-03-09 2:46 ` Anton Blanchard
2007-03-08 8:56 ` Christoph Hellwig
2007-03-08 9:42 ` Eric Dumazet
2007-03-08 10:21 ` Christoph Hellwig
2007-03-08 11:11 ` Eric Dumazet
2007-03-08 11:18 ` Christoph Hellwig
2007-03-08 15:52 ` Linus Torvalds
2007-03-08 16:58 ` [PATCH] VFS : Delay the dentry name generation on sockets and pipes Eric Dumazet
2007-03-08 18:29 ` Eric Dumazet
2007-03-09 10:18 ` [PATCH, take2] " Eric Dumazet
2007-03-09 18:22 ` Linus Torvalds
2007-03-10 1:21 ` [PATCH, take3] " Eric Dumazet
2007-03-08 20:00 ` [patch] epoll use a single inode Bob Copeland
[not found] <45ED046A.5010508@argo.co.il>
2007-03-06 7:27 ` Davide Libenzi
2007-03-05 21:25 Davide Libenzi
2007-03-05 21:52 ` Eric Dumazet
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.0703061745580.3661@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=avi@argo.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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®