[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705301503210.6272@alien.or.mcafeemobile.com>
Date: Wed, 30 May 2007 15:06:22 -0700 (PDT)
From: Davide Libenzi <davidel@...ilserver.org>
To: Ulrich Drepper <drepper@...hat.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, Jeff Garzik <jeff@...zik.org>,
Zach Brown <zach.brown@...cle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@....com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Syslets, Threadlets, generic AIO support, v6
On Wed, 30 May 2007, Ulrich Drepper wrote:
> You also have to be aware that open() is just one piece of the puzzle.
> What about socket()? I've cursed this interface many times before and
> now it's biting you: there is parameter to pass a flag. What about
> transferring file descriptors via Unix domain sockets? How can I decide
> the transferred descriptor should be in the private namespace?
Well, we can't just replicate/change every system call that creates a file
descriptor. So I'm for something like:
int sys_fdup(int fd, int flags);
So you basically create your fds with their native/existing system calls,
and then you dup/move them into the prefered fd space.
- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists