[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AE04DCF.6040908@zytor.com>
Date: Thu, 22 Oct 2009 21:19:27 +0900
From: "H. Peter Anvin" <hpa@...or.com>
To: mtk.manpages@...il.com
CC: Matt Helsley <matthltc@...ibm.com>,
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, mingo@...e.hu,
linux-api@...r.kernel.org, torvalds@...ux-foundation.org,
Alexey Dobriyan <adobriyan@...il.com>, roland@...hat.com,
Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [RFC][v8][PATCH 9/10]: Define clone3() syscall
On 10/22/2009 09:14 PM, Michael Kerrisk wrote:
>
> So, sometimes, a number in a system call should be the bit width of
> some arguments(s), sometimes it should be the number of arguments, and
> sometimes (well, just occasionally, as in mmap2() and clone()) -- it
> should be a version number? Does the weather play any part in the
> decision? ;-)
>
The notion is that they are *some* kind of description on how the system
call has been augmented. The bitwidths and argument numbers are
non-overlapping and visually very different, so are not subject to
confusion. Your argument makes about as much sense as saying the letter
"a" should have the same meaning in every context.
-hpa
--
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