OpenVZ Forum


Home » Mailing lists » Devel » Re: [PATCH 10/12] L2 network namespace: playing with pass-through device
Re: [PATCH 10/12] L2 network namespace: playing with pass-throughdevice [message #8991 is a reply to message #8988] Tue, 12 December 2006 14:26 Go to previous messageGo to previous message
Mishin Dmitry is currently offline  Mishin Dmitry
Messages: 112
Registered: February 2006
Senior Member
On Tuesday 12 December 2006 17:19, Daniel Lezcano wrote:
> Dmitry Mishin wrote:
>
> >>>> Why do yo need to have a child list and sibling list ?
> >>> Because of the level2<->level3 hierarchy, for example.
> >> This hierarchy doesn't exist with ns->parent ? Do you have an example
> >> when the hierarchy should be used ? I mean when we need to browse from
> >> l2 -> l3 ?
> > For example, to check that new ifaddr is already used by child l3 namespace.
>
> The devinet isolation does already do that, you can not add a new ifaddr
> if it already exists. Do you have another example ?
Could devinet isolation provide ifaddrs list with namespaces?
What will be with child namespaces if you decide to destroy parent namespace?
If we decide to destroy them, than how we could get their list?
It is a question of flexibility and easy management.
Why do you want to remove this code?

--
Thanks,
Dmitry.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: [PATCH 03/25] reintroduce list of vfsmounts over superblock
Next Topic: Re: Re: [patch -mm 08/17] nsproxy: add hashtable
Goto Forum:
  


Current Time: Sat Jul 26 06:31:28 GMT 2025

Total time taken to generate the page: 0.37414 seconds