netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jiri Pirko <jiri@resnulli.us>,
	netdev@vger.kernel.org, davem@davemloft.net, mlxsw@mellanox.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: Wed, 7 Aug 2019 14:55:14 -0600	[thread overview]
Message-ID: <c3cd420e-4071-c1b3-4ecb-c995f57ee8ed@gmail.com> (raw)
In-Reply-To: <20190807114918.15e10047@cakuba.netronome.com>

On 8/7/19 12:49 PM, Jakub Kicinski wrote:
> Perhaps I'm misinterpreting your point there.

yes, this thread is getting out of hand.

I am not pushing for an in-kernel, fib resource controller. Jiri wants
to remove the existing devlink resource code from netdevsim into a
standalone driver, code that was added for testing and as the commit log
shows as a demonstration of how one could create a controller using the
devlink API. I added some color commentary as to why a devlink
controller makes sense for the use case and how it should work, but I am
not asking for such a controller to be added to the kernel.

The netdevsim resource controller is counter based; the absolute
simplest form of limits. If I wanted basic counting for a fib resource
controller, I would add an option to limit the number of fib rules and
routes using sysctl similar to what exists for neighbors. Consistency. I
don't need the overhead and unrelated messiness of cgroups. I don't need
the overhead of handling fib notifiers. fib (rule) add -- check counter,
increment counter; fib (rule) delete -- decrement counter. Simple, per
namespace, done.

  reply	other threads:[~2019-08-07 20:55 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
2019-08-07 18:57           ` Jakub Kicinski
2019-08-07 18:49       ` Jakub Kicinski
2019-08-07 20:55         ` David Ahern [this message]
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=c3cd420e-4071-c1b3-4ecb-c995f57ee8ed@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 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).