[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091014013936.GC27627@count0.beaverton.ibm.com>
Date: Tue, 13 Oct 2009 18:39:36 -0700
From: Matt Helsley <matthltc@...ibm.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
randy.dunlap@...cle.com, arnd@...db.de,
Containers <containers@...ts.linux-foundation.org>,
Nathan Lynch <nathanl@...tin.ibm.com>,
linux-kernel@...r.kernel.org, Louis.Rilling@...labs.com,
"Eric W. Biederman" <ebiederm@...ssion.com>,
kosaki.motohiro@...fujitsu.com, linux-api@...r.kernel.org,
mingo@...e.hu, torvalds@...ux-foundation.org,
Alexey Dobriyan <adobriyan@...il.com>, roland@...hat.com,
Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [RFC][v8][PATCH 0/10] Implement clone3() system call
On Tue, Oct 13, 2009 at 04:49:05PM -0700, H. Peter Anvin wrote:
> On 10/12/2009 09:49 PM, Sukadev Bhattiprolu wrote:
> >
> > This patchset implements a new system call, clone3() that lets a process
> > specify the pids of the child process.
> >
>
> A system call named clone3() taking two parameters is just too weird to
> live. No, please.
Except we can't use clone2() because it conflicts on ia64. Care to propose
a name you would prefer?
Also I was a bit suprised to discover there are plenty of examples where this
convention has not been followed: vm86, lseek64, and mmap2 to name a few. In
fact, of the 46 __NR_foo[[:digit:]]+, 36 break this convention on x86-32.
Cheers,
-Matt Helsley
--
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