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. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
