[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.98.0705301457350.26602@woody.linux-foundation.org>
Date: Wed, 30 May 2007 15:01:47 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Davide Libenzi <davidel@...ilserver.org>
cc: Ulrich Drepper <drepper@...hat.com>, 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, Davide Libenzi wrote:
>
> I agree. What would be a good interface to allocate fds in such area? We
> don't want to replicate syscalls, so maybe a special new dup function?
I'd do it with something like "newfd = dup2(fd, NONLINEAR_FD)" or similar,
and just have NONLINEAR_FD be some magic value (for example, make it be
0x40000000 - the bit that says "private, nonlinear" in the first place).
But what's gotten lost in the current discussion is that we probably don't
actually _need_ such a private space. I'm just saying that if the *choice*
is between memory-mapped interfaces and a private fd-space, we should
probably go for the latter. "Everything is a file" is the UNIX way, after
all. But there's little reason to introduce private fd's otherwise.
Linus
-
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