From: Flavio Leitner <fbl@redhat.com>
To: netdev@vger.kernel.org, dev@openvswitch.org
Cc: Flavio Leitner <fbl@redhat.com>
Subject: [PATCH net-next 0/3] Allow openvswitch to query ports in another netns.
Date: Thu, 2 Nov 2017 17:04:35 -0200 [thread overview]
Message-ID: <20171102190438.2583-1-fbl@redhat.com> (raw)
Today Open vSwitch users are moving internal ports to other namespaces and
although packets are flowing OK, the userspace daemon can't find out basic
information like if the port is UP or DOWN, for instance.
This patchset extends openvswitch API to retrieve the current netnsid of
a port. It will be used by the userspace daemon to find out in which netns
the port is located.
This patchset also extends the rtnetlink getlink call to accept and operate
on a given netnsid. More details are available in each patch.
Jiri Benc (3):
net: export peernet2id_alloc
openvswitch: reliable interface indentification in port dumps
rtnetlink: use netnsid to query interface
include/uapi/linux/if_link.h | 1 +
include/uapi/linux/openvswitch.h | 2 +
net/core/net_namespace.c | 1 +
net/core/rtnetlink.c | 103 ++++++++++++++++++++++++++++++++-------
net/openvswitch/datapath.c | 47 +++++++++++++-----
net/openvswitch/datapath.h | 4 +-
net/openvswitch/dp_notify.c | 4 +-
7 files changed, 127 insertions(+), 35 deletions(-)
--
2.13.6
next reply other threads:[~2017-11-02 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 19:04 Flavio Leitner [this message]
2017-11-02 19:04 ` [PATCH net-next 1/3] net: export peernet2id_alloc Flavio Leitner
2017-11-02 19:04 ` [PATCH net-next 2/3] openvswitch: reliable interface indentification in port dumps Flavio Leitner
2017-11-02 19:04 ` [PATCH net-next 3/3] rtnetlink: use netnsid to query interface Flavio Leitner
2017-11-05 12:50 ` [PATCH net-next 0/3] Allow openvswitch to query ports in another netns David Miller
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=20171102190438.2583-1-fbl@redhat.com \
--to=fbl@redhat.com \
--cc=dev@openvswitch.org \
--cc=netdev@vger.kernel.org \
/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).