From: Stephen Hemminger <shemming@brocade.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2-next 2/2] netns: allow to dump and monitor nsid
Date: Mon, 20 Apr 2015 10:02:42 -0700 [thread overview]
Message-ID: <20150420100242.0b21a78e@urahara> (raw)
In-Reply-To: <797e9129b12148228f163402c284dce6@HQ1WP-EXMB12.corp.brocade.com>
On Thu, 9 Apr 2015 08:30:14 +0000
Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
> Two commands are added:
> - ip netns list-id
> - ip monitor nsid
>
> A cache is also added to remember the association between the iproute2 netns
> name (from /var/run/netns/) and the nsid.
> To avoid interfering with the rth socket, a new rtnl socket (rtnsh) is used to
> get nsid (we may send rtnl request during listing on rth).
>
> Example:
> $ ip netns list-id
> nsid 0 (iproute2 netns name: foo)
> $ ip monitor nsid
> Deleted nsid 0 (iproute2 netns name: foo)
> nsid 16 (iproute2 netns name: bar)
>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Applied with a couple of little style cleanups.
prev parent reply other threads:[~2015-04-20 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 8:30 [PATCH iproute2-next 1/2] include: update linux/rtnetlink.h Nicolas Dichtel
2015-04-09 8:30 ` [PATCH iproute2-next 2/2] netns: allow to dump and monitor nsid Nicolas Dichtel
2015-04-09 8:36 ` Vadim Kochan
2015-04-10 14:03 ` Nicolas Dichtel
2015-04-09 8:48 ` Vadim Kochan
2015-04-10 14:03 ` Nicolas Dichtel
2015-04-15 12:23 ` [PATCH v2 iproute2] " Nicolas Dichtel
2015-04-10 20:24 ` [PATCH iproute2-next 1/2] include: update linux/rtnetlink.h Stephen Hemminger
[not found] ` <797e9129b12148228f163402c284dce6@HQ1WP-EXMB12.corp.brocade.com>
2015-04-20 17:02 ` Stephen Hemminger [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=20150420100242.0b21a78e@urahara \
--to=shemming@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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).