From: Jiri Pirko <jiri@resnulli.us>
To: David Ahern <dsahern@gmail.com>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
netdev@vger.kernel.org, davem@davemloft.net,
sthemmin@microsoft.com, mlxsw@mellanox.com
Subject: Re: [patch net-next v2 1/3] net: devlink: allow to change namespaces
Date: Fri, 2 Aug 2019 09:43:31 +0200 [thread overview]
Message-ID: <20190802074331.GB2203@nanopsycho> (raw)
In-Reply-To: <087f584d-06c5-f4b9-722b-ccb72ce0e5de@gmail.com>
Wed, Jul 31, 2019 at 09:46:13PM CEST, dsahern@gmail.com wrote:
>On 7/31/19 1:45 PM, Jiri Pirko wrote:
>>> check. e.g., what happens if a resource controller has been configured
>>> for the devlink instance and it is moved to a namespace whose existing
>>> config exceeds those limits?
>>
>> It's moved with all the values. The whole instance is moved.
>>
>
>The values are moved, but the FIB in a namespace could already contain
>more routes than the devlink instance allows.
There is no relation between fib and devlink.
>
next prev parent reply other threads:[~2019-08-02 7:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 8:57 [patch net-next v2 0/3] net: devlink: Finish network namespace support Jiri Pirko
2019-07-30 8:57 ` [patch net-next v2 1/3] net: devlink: allow to change namespaces Jiri Pirko
2019-07-30 22:39 ` Jakub Kicinski
2019-07-31 19:26 ` Jiri Pirko
2019-07-31 19:41 ` David Ahern
2019-07-31 19:45 ` Jiri Pirko
2019-07-31 19:46 ` David Ahern
2019-07-31 19:58 ` David Ahern
2019-07-31 20:20 ` David Ahern
2019-08-02 7:48 ` Jiri Pirko
2019-08-02 15:45 ` David Ahern
2019-08-05 5:54 ` Jiri Pirko
2019-08-05 14:10 ` David Ahern
2019-08-05 14:49 ` Jiri Pirko
2019-08-05 14:51 ` David Ahern
2019-08-05 15:20 ` Jiri Pirko
2019-08-06 17:34 ` David Ahern
2019-08-06 17:53 ` Jiri Pirko
2019-08-06 17:55 ` David Ahern
2019-08-06 18:07 ` Jiri Pirko
2019-08-02 7:43 ` Jiri Pirko [this message]
2019-07-30 8:57 ` [patch net-next v2 2/3] net: devlink: export devlink net set/get helpers Jiri Pirko
2019-07-30 22:40 ` Jakub Kicinski
2019-07-30 8:57 ` [patch net-next v2 3/3] netdevsim: create devlink and netdev instances in namespace Jiri Pirko
2019-07-30 22:40 ` Jakub Kicinski
2019-07-30 8:59 ` [patch iproute2-next v2 1/2] devlink: introduce cmdline option to switch to a different namespace Jiri Pirko
2019-07-30 8:59 ` [patch iproute2-next v2 2/2] devlink: add support for network namespace change Jiri Pirko
2019-07-31 22:59 ` [patch net-next v2 0/3] net: devlink: Finish network namespace support 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=20190802074331.GB2203@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox