From: David Ahern <dsahern@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, davem@davemloft.net, mlxsw@mellanox.com,
jakub.kicinski@netronome.com, f.fainelli@gmail.com,
vivien.didelot@gmail.com, mkubecek@suse.cz,
stephen@networkplumber.org, daniel@iogearbox.net,
brouer@redhat.com, eric.dumazet@gmail.com
Subject: Re: [RFC] implicit per-namespace devlink instance to set kernel resource limitations
Date: Tue, 6 Aug 2019 21:10:40 -0600 [thread overview]
Message-ID: <153eb34b-05dd-4a85-88d8-e5723f41bbe3@gmail.com> (raw)
In-Reply-To: <20190807025933.GF20422@lunn.ch>
On 8/6/19 8:59 PM, Andrew Lunn wrote:
> However, zoom out a bit, from networking to the whole kernel. In
> general, across the kernel as a whole, resource management is done
> with cgroups. cgroups is the consistent operational model across the
> kernel as a whole.
>
> So i think you need a second leg to your argument. You have said why
> devlink is the right way to do this. But you should also be able to
> say to Tejun Heo why cgroups is the wrong way to do this, going
> against the kernel as a whole model. Why is networking special?
>
So you are saying mlxsw should be using a cgroups based API for its
resources? netdevsim is for testing kernel APIs sans hardware. Is that
not what the fib controller netdevsim is doing? It is from my perspective.
I am not the one arguing to change code and functionality that has
existed for 16 months. I am arguing that the existing resource
controller satisfies all existing goals (testing in kernel APIs) and
even satisfies additional ones - like a consistent user experience
managing networking resources. ie.., I see no reason to change what exists.
next prev parent reply other threads:[~2019-08-07 3:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 16:40 [RFC] implicit per-namespace devlink instance to set kernel resource limitations Jiri Pirko
2019-08-06 17:38 ` David Ahern
2019-08-06 18:03 ` Andrew Lunn
2019-08-07 2:33 ` David Ahern
2019-08-07 2:59 ` Andrew Lunn
2019-08-07 3:10 ` David Ahern [this message]
2019-08-07 18:57 ` Jakub Kicinski
2019-08-07 18:49 ` Jakub Kicinski
2019-08-07 20:55 ` David Ahern
2019-08-06 18:27 ` Jakub Kicinski
2019-08-06 18:38 ` Jiri Pirko
2019-08-06 18:54 ` Jakub Kicinski
2019-08-06 19:06 ` Andrew Lunn
2019-08-08 18:03 ` Jonathan Lemon
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=153eb34b-05dd-4a85-88d8-e5723f41bbe3@gmail.com \
--to=dsahern@gmail.com \
--cc=andrew@lunn.ch \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=mkubecek@suse.cz \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vivien.didelot@gmail.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.