Messages in this thread | | | Date | Wed, 06 Jun 2007 16:08:17 -0700 (PDT) | Subject | Re: [patch 7/8] fdmap v2 - implement sys_socket2 | From | David Miller <> |
| |
From: Davide Libenzi <davidel@xmailserver.org> Date: Wed, 6 Jun 2007 16:04:40 -0700 (PDT)
> On Wed, 6 Jun 2007, Alan Cox wrote: > > > > The sys_accept() system call has been modified to return a file > > > descriptor inside the non-sequential area, if the listening fd is. > > > The sys_socketcall() system call has been also changed to support > > > a new SYS_SOCKET2 indentifier. > > > > This still all seems really really ugly. Is there anything wrong with > > throwing all these extra cases out and replacing the entire lot with > > > > prctl(PR_SPARSEFD, 1); > > > > to turn on sparse fd allocation for a process ? > > There was a little discussion where I tried to whisper something similar, > but Linus and Uli shot me :) - with good reasons IMO. > You may link to runtimes that are not non-sequentialfd aware, and will > break them.
Thanks for explaining this issue clearly instead of telling people to "go read the archives" in a condescending manner like someone else did. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |