From: David Ahern <dsahern@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
jakub.kicinski@netronome.com, sthemmin@microsoft.com,
mlxsw@mellanox.com
Subject: Re: [patch net-next 0/3] net: devlink: Finish network namespace support
Date: Wed, 31 Jul 2019 15:50:26 -0600 [thread overview]
Message-ID: <8f5afc58-1cbc-9e9a-aa15-94d1bafcda22@gmail.com> (raw)
In-Reply-To: <20190730060817.GD2312@nanopsycho.orion>
On 7/30/19 12:08 AM, Jiri Pirko wrote:
> Mon, Jul 29, 2019 at 10:17:25PM CEST, dsahern@gmail.com wrote:
>> On 7/27/19 3:44 AM, Jiri Pirko wrote:
>>> From: Jiri Pirko <jiri@mellanox.com>
>>>
>>> Devlink from the beginning counts with network namespaces, but the
>>> instances has been fixed to init_net. The first patch allows user
>>> to move existing devlink instances into namespaces:
>>>
>>
>> so you intend for an asic, for example, to have multiple devlink
>> instances where each instance governs a set of related ports (e.g.,
>> ports that share a set of hardware resources) and those instances can be
>> managed from distinct network namespaces?
>
> No, no multiple devlink instances for asic intended.
So it should be allowed for an asic to have resources split across
network namespaces. e.g., something like this:
namespace 1 | namespace 2 | ... | namespace N
| | |
{ ports 1 } | { ports 2 } | ... | { ports N }
| | |
devlink 1 | devlink 2 | ... | devlink N
=================================================
driver
next prev parent reply other threads:[~2019-07-31 21:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 9:44 [patch net-next 0/3] net: devlink: Finish network namespace support Jiri Pirko
2019-07-27 9:44 ` [patch net-next 1/3] net: devlink: allow to change namespaces Jiri Pirko
2019-07-29 17:52 ` David Miller
2019-07-30 6:05 ` Jiri Pirko
2019-07-27 9:44 ` [patch net-next 2/3] net: devlink: export devlink net set/get helpers Jiri Pirko
2019-07-27 9:44 ` [patch net-next 3/3] netdevsim: create devlink and netdev instances in namespace Jiri Pirko
2019-07-29 18:59 ` Jakub Kicinski
2019-07-30 6:06 ` Jiri Pirko
2019-07-30 17:14 ` Jakub Kicinski
2019-07-30 21:03 ` Jiri Pirko
2019-07-27 10:05 ` [patch iproute2 1/2] devlink: introduce cmdline option to switch to a different namespace Jiri Pirko
2019-07-27 10:12 ` Toke Høiland-Jørgensen
2019-07-27 10:21 ` Jiri Pirko
2019-07-27 10:25 ` Toke Høiland-Jørgensen
2019-07-29 20:21 ` David Ahern
2019-07-30 6:07 ` Jiri Pirko
2019-07-29 20:17 ` David Ahern
2019-07-27 10:05 ` [patch iproute2 2/2] devlink: add support for network namespace change Jiri Pirko
2019-07-29 20:17 ` [patch net-next 0/3] net: devlink: Finish network namespace support David Ahern
2019-07-30 6:08 ` Jiri Pirko
2019-07-31 21:50 ` David Ahern [this message]
2019-07-31 22:02 ` Jakub Kicinski
2019-07-31 22:07 ` David Ahern
2019-07-31 22:28 ` Jakub Kicinski
2019-07-31 22:31 ` David Ahern
2019-08-02 7:42 ` Jiri Pirko
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=8f5afc58-1cbc-9e9a-aa15-94d1bafcda22@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.