From: Oliver Hartkopp <oliver@hartkopp.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Containers <containers@lists.osdl.org>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Tejun Heo <htejun@gmail.com>, Greg Kroah-Hartman <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Urs Thuermann <urs@isnogud.escape.de>
Subject: Re: Network Namespace status
Date: Fri, 14 Sep 2007 08:03:56 +0200 [thread overview]
Message-ID: <46EA244C.1050702@hartkopp.net> (raw)
In-Reply-To: <m18x7a5qif.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
> Looking into my patch queue I have:
> 5 patches for cleaning up and making a per network namespace loopback device.
> 4 patches for making rtnetlink message processing per network namespace
> 1 patch for making AF_UNIX per network namespace
> 1 patch for making AF_PACKET per network namespace
>
> The ipv4 part of my patchset is currently working but it needs some
> more cleanup and reordering of patches before it is ready to go anywhere.
> Nothing has been done for ipv6, but the changes should very much parallel
> ipv4.
>
> The other protocols I haven't even looked at yet.
>
Hi Eric,
can you send me your current AF_PACKET patch? I just want to update our
recent post of the CAN (controller area network) subsystem (AF_CAN)
which is (in some parts) similar to AF_PACKET. So i can take a look on
it to provide the latest technique in the next post ...
Thanks,
Oliver
next prev parent reply other threads:[~2007-09-14 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:12 Network Namespace status Eric W. Biederman
2007-09-14 6:03 ` Oliver Hartkopp [this message]
2007-09-14 9:33 ` Eric W. Biederman
2007-09-16 22:36 ` David Miller
2007-09-16 23:47 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2008-02-15 15:31 Network namespace status Daniel Lezcano
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=46EA244C.1050702@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=urs@isnogud.escape.de \
/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).