From: Daniel Lezcano <daniel.lezcano@free•fr>
To: "Martín Ferrari" <martin.ferrari@gmail•com>
Cc: netdev <netdev@vger•kernel.org>,
Mathieu Lacage <mathieu.lacage@sophia•inria.fr>
Subject: Re: Namespaces and devices
Date: Tue, 25 May 2010 12:14:38 +0200 [thread overview]
Message-ID: <4BFBA30E.4040304@free.fr> (raw)
In-Reply-To: <AANLkTimp16eLIO7F65t7-hFgXGbVnoEIW3jGhzWTJlYa@mail.gmail.com>
On 05/25/2010 11:56 AM, Martín Ferrari wrote:
> Hi Daniel,
>
> On Sun, May 23, 2010 at 16:04, Daniel Lezcano<daniel.lezcano@free•fr> wrote:
>
>
>> The documentation on this website is a bit out dated. That was the initial
>> behavior but was changed as the following.
>>
>> All the virtual devices are destroyed with the network namespace. The
>> destroyable virtual devices are identified when they have the dellink ops
>> defined. If you can do the 'ip link del' command on this device, then this
>> device type will be destroyed by a netns.
>>
> Fair enough, thanks for the explanation.
>
You are welcome ;)
>> About the oops, was the it "kernel panic when using
>> netns+bridges+tc(netem)" ?
>>
> No, this is a different issue. Probably it got lost in the noise of
> the thread, but it is here:
> http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/694830/focus=158583
> (it is my second mail in that thread)
Ok, I was able to reproduce it easily. If I have spare time this week, I
will look at the oops.
>>> Also, I have read somewhere (now I cannot find it) that supposedly, I
>>> should be able to move real devices to a netns, but I always get
>>> Invalid argument errors.
>>>
>> Yes, that was previously the case with the proof of concept, because sysfs
>> per namespace was enabled. But this feature is not merged upstream yet (but
>> is on the way), so physical devices are not movable across namespaces.
>>
> OK. The plan is for them to return to netns 1 automatically at destroy?
>
Yes, this is the plan.
Thanks
-- Daniel
prev parent reply other threads:[~2010-05-25 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 16:27 Namespaces and devices Martín Ferrari
2010-05-23 14:04 ` Daniel Lezcano
2010-05-25 9:56 ` Martín Ferrari
2010-05-25 10:14 ` Daniel Lezcano [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=4BFBA30E.4040304@free.fr \
--to=daniel.lezcano@free$(echo .)fr \
--cc=martin.ferrari@gmail$(echo .)com \
--cc=mathieu.lacage@sophia$(echo .)inria.fr \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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