[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AD6557D.3090501@zytor.com>
Date: Wed, 14 Oct 2009 15:49:33 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
CC: Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org,
Oren Laadan <orenl@...columbia.edu>, serue@...ibm.com,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Pavel Emelyanov <xemul@...nvz.org>,
Andrew Morton <akpm@...l.org>, torvalds@...ux-foundation.org,
mikew@...gle.com, mingo@...e.hu,
Nathan Lynch <nathanl@...tin.ibm.com>, arnd@...db.de,
peterz@...radead.org, Louis.Rilling@...labs.com,
kosaki.motohiro@...fujitsu.com, randy.dunlap@...cle.com,
linux-api@...r.kernel.org,
Containers <containers@...ts.linux-foundation.org>,
sukadev@...ibm.com
Subject: Re: [RFC][v8][PATCH 0/10] Implement clone3() system call
On 10/14/2009 03:36 PM, Sukadev Bhattiprolu wrote:
> H. Peter Anvin [hpa@...or.com] wrote:
> |
> | Overall it seems sane to:
> |
> | a) make it an actual 3-argument call;
> | b) make the existing flags a u32 forever, and make it a separate
> | argument;
> | c) any new expansion can be via the struct, which may want to have
> | an "c3_flags" field first in the structure.
>
> Ok, So will this work ?
>
> struct clone_args {
> u32 flags_high; /* new clone flags (higher bits) */
> u32 reserved1;
> u32 nr_pids;
> u32 reserved2;
> u64 child_stack_base;
> u64 child_stack_size;
> u64 parent_tid_ptr;
> u64 child_tid_ptr;
> u64 reserved3;
> };
>
> sys_clone3(u32 flags_low, struct clone_args *args, pid_t *pid_list)
>
> Even on 64bit architectures the applications have to use sys_clone3() for
> the extended features.
Yes, although I'd just make flags_high a u64. The other thing that
might be worthwhile is to have a length field on the structure; that way
we could add new fields at the end if ever necessary in the future.
-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