From: Linus Torvalds <torvalds@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Ulrich Drepper <drepper@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap
Date: Sun, 3 Jun 2007 22:11:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0706032210040.23741@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706031311490.13247@alien.or.mcafeemobile.com>
On Sun, 3 Jun 2007, Davide Libenzi wrote:
>
> Agreed, a new syscall looks less messy. I'll make sys_dup2() to allow
> installing in the non-sequential area, only if there's an fd already
> allocated. F_DUPFD will remain unchanged (that is, not allow
> non-sequential fds allocations).
I actually think that a new system call is _hugely_ messy. It means that
anybody who wants to use a new feature needs to have a new glibc. Not
nice, not nice at all. I'd much rather see a totally transparent extension
that doesn't require any new user space what-so-ever to be used...
Linus
next prev parent reply other threads:[~2007-06-04 5:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 22:59 Davide Libenzi
2007-06-03 6:43 ` Ingo Molnar
2007-06-03 18:22 ` Davide Libenzi
2007-06-03 18:20 ` Ulrich Drepper
2007-06-03 18:53 ` Davide Libenzi
2007-06-03 19:43 ` Ulrich Drepper
2007-06-03 20:19 ` Davide Libenzi
2007-06-03 20:46 ` Ulrich Drepper
2007-06-03 23:01 ` Davide Libenzi
2007-06-03 23:09 ` Ulrich Drepper
2007-06-03 23:32 ` Davide Libenzi
2007-06-04 5:11 ` Linus Torvalds [this message]
2007-06-04 5:22 ` Ulrich Drepper
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=alpine.LFD.0.98.0706032210040.23741@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®