From: Dmitry Mishin <dim@openvz.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
Daniel Lezcano <dlezcano@fr.ibm.com>, Kirill Korotaev <dev@sw.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Herbert Poetzl <herbert@13thfloor.at>,
"Eric W. Biederman" <ebiederm@xmission.com>,
netdev@vger.kernel.org
Subject: Re: [patch -mm] net namespace: empty framework
Date: Wed, 22 Nov 2006 19:55:56 +0300 [thread overview]
Message-ID: <200611221955.56942.dim@openvz.org> (raw)
In-Reply-To: <20061122164154.GB17378@sergelap.austin.ibm.com>
On Wednesday 22 November 2006 19:41, Serge E. Hallyn wrote:
> Quoting Cedric Le Goater (clg@fr.ibm.com):
> > Hello,
> >
> > Dmitry Mishin wrote:
> >
> > > This patch looks acceptable for us.
> >
> > good. shall we merge it then ? see comment below.
> >
> > > BTW, Daniel, we agreed to be based on the Andrey's patchset. I do not see a
> > > reason, why Cedric force us to make some unnecessary work and move existent
> > > patchset over his interface.
> >
> > yeah it's a bit different from andrey's but not that much and it's more in
>
> Where is Andrey's patch?
This thread - http://thread.gmane.org/gmane.linux.network/42666
>
> > the spirit of uts and ipc namespace (and user namespace if that reaches the
> > kernel one day :) so that's why i made the small changes.
>
> I agree the namespace frameworks should be consistent, but i don't know
> whether Andrey's is or not. I'd like to have the framework included so
> we reduce the number of silly rewrites due to clone flag collisions etc.
>
> >
> > It also helping the nsproxy/namespace syscalls to have a similar interface
> > to manipulate namespaces. who knows, soon we might be able to have a 'struct
> > namespace' with a ops field to define new namespace types ?
> >
> > I can also send a empty framework for user namespace ;)
>
> Please do - then I'll rebase the patchset I sent to the containes list
> onto your patch, and resubmit the whole userns.
>
> -serge
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Thanks,
Dmitry.
next prev parent reply other threads:[~2006-11-22 16:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 13:34 [patch -mm] net namespace: empty framework Cedric Le Goater
2006-11-21 13:51 ` Kirill Korotaev
2006-11-21 18:01 ` Daniel Lezcano
2006-11-21 18:16 ` Herbert Poetzl
2006-11-22 13:46 ` Cedric Le Goater
2006-11-22 17:53 ` Eric W. Biederman
2006-11-22 22:56 ` Daniel Lezcano
2006-11-23 9:05 ` Dmitry Mishin
2006-11-22 8:21 ` Dmitry Mishin
2006-11-22 8:43 ` Eric W. Biederman
2006-11-22 13:23 ` Kirill Korotaev
2006-11-22 13:34 ` Dmitry Mishin
2006-11-22 9:55 ` Daniel Lezcano
2006-11-22 13:53 ` Cedric Le Goater
2006-11-22 16:41 ` Serge E. Hallyn
2006-11-22 16:55 ` Dmitry Mishin [this message]
2006-11-23 2:39 ` Serge E. Hallyn
2006-11-23 9:07 ` Dmitry Mishin
2006-11-23 9:24 ` Cedric Le Goater
2006-11-29 17:59 ` Daniel Lezcano
2006-11-22 16:57 ` Cedric Le Goater
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=200611221955.56942.dim@openvz.org \
--to=dim@openvz.org \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=serue@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.