public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg@fr.ibm.com>
To: Kirill Korotaev <dev@parallels.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	"David C. Hansen" <haveblue@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	Containers <containers@lists.osdl.org>,
	Pavel Emelyanov <xemul@openvz.org>
Subject: Re: [PATCH 1/3] change clone_flags type to u64
Date: Thu, 10 Apr 2008 15:23:00 +0200	[thread overview]
Message-ID: <47FE14B4.4090705@fr.ibm.com> (raw)
In-Reply-To: <47FE1219.5010405@parallels.com>

Kirill Korotaev wrote:
> The was no real rationale except for some people seeing "clone" functionality
> as the match and the fact that FS_NAMESCAPE was done so made them believe it 
> is a good way to go.
> And I warned about flags limitation at the beginning.

yes and now, we've hit the clone wall but that's a good thing.

> Both OpenVZ/vserver suggested to use a special syscall for handling this.

most projects do it that way.

> Maybe it is a good point to switch to it now finally and stop worring about all 
> this?

what would be the interface ? 

C. 

 

  reply	other threads:[~2008-04-10 13:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 22:26 [PATCH 0/3] clone64() and unshare64() system calls sukadev
2008-04-09 22:32 ` [PATCH 1/3] change clone_flags type to u64 sukadev
2008-04-10  8:25   ` Andi Kleen
2008-04-10 12:25     ` Cedric Le Goater
2008-04-10 12:52       ` Andi Kleen
2008-04-10 13:11         ` Kirill Korotaev
2008-04-10 13:23           ` Cedric Le Goater [this message]
2008-04-10 13:18         ` Cedric Le Goater
2008-04-10 17:14         ` Serge E. Hallyn
2008-04-10 22:13           ` Daniel Hokka Zakrisson
2008-04-10 22:49             ` Serge E. Hallyn
2008-04-11  8:45               ` Daniel Hokka Zakrisson
2008-04-09 22:34 ` [PATCH 2/3] add do_unshare() sukadev
2008-04-09 22:34 ` [PATCH 3/3] add the clone64() and unshare64() syscalls sukadev
2008-04-09 23:07   ` Jakub Jelinek
2008-04-10  2:15     ` sukadev
2008-04-10  3:40       ` H. Peter Anvin
2008-04-10  0:00 ` [PATCH 0/3] clone64() and unshare64() system calls H. Peter Anvin
2008-04-10  1:07   ` sukadev
2008-04-10  1:10     ` H. Peter Anvin
2008-04-10  2:38       ` sukadev
2008-04-10  2:43         ` Paul Menage
2008-04-10 18:26           ` sukadev
2008-04-10 18:31             ` H. Peter Anvin
2008-04-10 12:33       ` Cedric Le Goater
2008-04-10 16:00         ` H. Peter Anvin
2008-04-10  6:48   ` Cedric Le Goater
  -- strict thread matches above, loose matches on Subject: below --
2008-02-11  9:58 [patch 0/3] clone64() and unshare64() syscalls clg
2008-02-11  9:58 ` [patch 1/3] change clone_flags type to u64 clg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FE14B4.4090705@fr.ibm.com \
    --to=clg@fr.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=containers@lists.osdl.org \
    --cc=dev@parallels.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xemul@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox