[RFC][v7][PATCH 8/9]: Define clone2() syscall
H. Peter Anvin
hpa at zytor.com
Tue Sep 29 13:02:15 PDT 2009
On 09/29/2009 12:10 PM, Linus Torvalds wrote:
> On Tue, 29 Sep 2009, Arjan van de Ven wrote:
>>> We already have a syscall layer which is painful to thunk in places,
>>> and this would make it much worse.
>> syscalls are cheap as well.
>> cheaper than decades of dealing with such multiplexer mess ;/
> Well, I'd agree, except the clone flags really _are_ about multiplexer
> issues, and the new flag woudln't really change anything.
> If the new system call actually had appreciably separate code-paths, I'd
> buy the "multiplexer" argument. But it doesn't really. It's going to call
> down to the same basic clone functionality, and the core clone code ends
> up de-multiplexing the cases anyway.
> So this would not at all be like the socket calls (to pick the traditional
> Linux system call multiplexing example) in that sense.
That's not the main issue here, though. The main issue is that the
prototype of the function now depends on one of its arguments, which is
absolute hell for anything that needs to thunk arguments in a systematic
way, which we have to do on several architectures, and which would be
useful to be able to do for others, too.
More information about the Containers