[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171105.215005.784375864325514764.davem@davemloft.net>
Date:   Sun, 05 Nov 2017 21:50:05 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     fbl@...hat.com
Cc:     netdev@...r.kernel.org, dev@...nvswitch.org
Subject: Re: [PATCH net-next 0/3] Allow openvswitch to query ports in
 another netns.
From: Flavio Leitner <fbl@...hat.com>
Date: Thu,  2 Nov 2017 17:04:35 -0200
> 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.
Series applied, thanks Flavio.
Powered by blists - more mailing lists
 
