From: Cedric Le Goater <clg@fr.ibm.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>, Kirill Korotaev <dev@sw.ru>,
Cedric Le Goater <clg@fr.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Dmitry Mishin <dim@sw.ru>,
netdev@vger.kernel.org
Subject: Re: [patch -mm] net namespace: empty framework
Date: Wed, 22 Nov 2006 14:46:44 +0100 [thread overview]
Message-ID: <456454C4.5010803@fr.ibm.com> (raw)
In-Reply-To: <20061121181655.GA14656@MAIL.13thfloor.at>
> no problem here, but I think we will need another one,
> or some smart way to do the network isolation (layer 3)
> for the network namespace (as alternative to the layer 2
> approach) ...
My feeling (Dmitry and Daniel can correct me) is that it will be
addressed with an unshare-like flag : NETNS2 and NETNS3.
> as they are both complementary in some way, I'm not sure
> a single space will suffice ...
hmm, so you think there could be a 2 differents namespaces
for network to handle layer 2 or 3. Couldn't that be just a sub part
of net_namespace.
C.
next prev parent reply other threads:[~2006-11-22 13:46 UTC|newest]
Thread overview: 20+ 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 [this message]
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
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-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=456454C4.5010803@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=dim@sw.ru \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).