From: ebiederm@xmission.com (Eric W. Biederman)
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: netdev@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>,
David Stevens <dlstevens@us.ibm.com>
Subject: Re: network namespace website
Date: Fri, 06 Apr 2007 15:03:20 -0600 [thread overview]
Message-ID: <m164895i7b.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <46164A9E.2090705@fr.ibm.com> (Daniel Lezcano's message of "Fri, 06 Apr 2007 15:26:54 +0200")
Daniel Lezcano <dlezcano@fr.ibm.com> writes:
> Hi,
>
> Eric Biederman has posted a few weeks ago a RFC-patchset concerning the
> network namespace.
> I ported it to the 2.6.20 kernel and uploaded the patchset to
>
> http://lxc.sourceforge.net/network.php
>
> For the part I had to used (TCP/UDP-IPV4 with usual ethernet device), I
> found the patchset pretty stable.
>
> You can find in the website:
>
> - a global description of what is the network namespace
> - a howto for the network namespace configuration
> - a benchmarking matrix
> - the network namespace patchset for 2.6.20 kernel
>
> I hope that can helps to answer what is ? , what for ?, how to use ?
> questions.
>
> If you have any questions or feedbacks, feel free to send an email to
> containers@ mailing list
An updated version with hopefully all of the fixes applied and merged
based into the proper patches and against against 2.6.21-rc6 is available at:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/linux-2.6-netns.git
After finally getting the sysfs support back under control I have finished
rebasing my original patchset.
Eric
prev parent reply other threads:[~2007-04-06 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 13:26 network namespace website Daniel Lezcano
2007-04-06 21:03 ` Eric W. Biederman [this message]
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=m164895i7b.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=containers@lists.osdl.org \
--cc=dlezcano@fr.ibm.com \
--cc=dlstevens@us.ibm.com \
--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 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.