[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <m18x76xje3.fsf@ebiederm.dsl.xmission.com>
Date: Sun, 16 Sep 2007 17:47:32 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: David Miller <davem@...emloft.net>
Cc: containers@...ts.osdl.org, netdev@...r.kernel.org,
htejun@...il.com, gregkh@...e.de, akpm@...ux-foundation.org
Subject: Re: Network Namespace status
David Miller <davem@...emloft.net> writes:
> From: ebiederm@...ssion.com (Eric W. Biederman)
> Date: Thu, 13 Esp 2007 13:12:08 -0600
>
>> The final blocker to having multiple useful instances of network
>> namespaces is the loopback device. We recognize the network namespace
>> of incoming packets by looking at dev->nd_net. Which means for
>> packets to properly loopback within a network namespace we need a
>> loopback device per network namespace. There were some concerns
>> expressed when we posted the cleanup part of the patches that allowed
>> for multiple loopback devices a few weeks ago so resolving this one
>> may be tricky.
>
> There was a change posted recently to dynamically allocate the
> loopback device. I like that (sorry I don't have a reference
> to the patch handy), and you can build on top of that to get
> the namespace local loopback objects you want.
>
> static struct net_device *loopback_dev(struct net_namespace *net)
> {
> ...
> }
>
> You get the idea.
Sure. Thanks.
Since the change got dropped I figured it for a rejection, and that
I would have to rework that patch.
On a similar note. It recently occurred to me that I can make creating
multiple network namespaces depend on !CONFIG_SYSFS. Which will allow
most of the rest of the patches I am sure of to be merged now. And
give me just a little more time to work with Tejun and finish up the
sysfs support.
Eric
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists