Re: [RFC PATCH net-next v2 0/5] netns: allow to identify peer netns

[Nicolas Dichtel]

Le 02/10/2014 21:20, Eric W. Biederman a Ãcrit :
> Nicolas Dichtel <nicolas.dichtel@xxxxxxxxx> writes:
>
> > Le 29/09/2014 20:43, Eric W. Biederman a Ãcrit :
> > > Nicolas Dichtel <nicolas.dichtel@xxxxxxxxx> writes:
> > >
> > > > Le 26/09/2014 20:57, Eric W. Biederman a Ãcrit :
> > > > > Andy Lutomirski <luto@xxxxxxxxxxxxxx> writes:
> > > > >
> > > > > > On Fri, Sep 26, 2014 at 11:10 AM, Eric W. Biederman
> > > > > > <ebiederm@xxxxxxxxxxxx> wrote:
> > > > > > > I see two ways to go with this.
> > > > > > >
> > > > > > > - A per network namespace table to that you can store ids for ``peer''
> > > > > > >      network namespaces.  The table would need to be populated manually by
> > > > > > >      the likes of ip netns add.
> > > > > > >
> > > > > > >      That flips the order of assignment and makes this idea solid.
> > > > I have a preference for this solution, because it allows to have a full
> > > > broadcast messages. When you have a lot of network interfaces (> 10k),
> > > > it saves a lot of time to avoid another request to get all informations.
> > >
> > > My practical question is how often does it happen that we care?
> > In fact, I don't think that scenarii with a lot of netns have a full mesh of
> > x-netns interfaces. It will be more one "link" netns with the physical
> > interface and all other with one interface with the link part in this "link"
> > netns. Hence, only one nsid is needing in each netns.
>
> I will buy that a full mesh is unlikely.
>
> For people doing simulations anything physical has a limited number of
> links.
>
> For people wanting all to all connectivity setting up an internal
> macvlan (or the equivalent) is likely much simpler and more efficient
> that a full mesh.
>
> So the question in my mind is how do we create these identifiers at need
> (when we create the cross network namespace links) instead of at network
> namespace creation time.  I don't see an answer to that in your patches,
> and perhaps it obvious.
For me, it is the responsability of the user who creates the netns. He should
know what will be done with this new netns, hence he may or may not define an
id. It's also possible to delegate this to the user who will create the tunnel.
In other words, it's part of the configuration.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/