From: Tejun Heo <tj@kernel.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, cgroups@vger.kernel.org,
shm@cumulusnetworks.com, roopa@cumulusnetworks.com
Subject: Re: [RFC PATCH net-next] net: Add l3mdev cgroup
Date: Mon, 4 Jan 2016 14:23:01 -0500 [thread overview]
Message-ID: <20160104192301.GC3807@mtj.duckdns.org> (raw)
In-Reply-To: <568AC534.1070308@cumulusnetworks.com>
Hello, David.
On Mon, Jan 04, 2016 at 12:17:08PM -0700, David Ahern wrote:
> None of the existing subsystems are relevant for configuring an L3
> networking domain, and it does not make sense to tie net_cls and net_prio to
> an L3 domain.
I don't have an answer for that but cgroup isn't a place to put such
stray configurations either. Please figure out where the
configuration belongs first. What you're proposing really isn't a
resource controller. There's no resource being distributed
hierarchically. It's just dumping configuration which hasn't found
its proper place into cgroup.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-01-04 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 16:32 [RFC PATCH net-next] net: Add l3mdev cgroup David Ahern
[not found] ` <1451925136-13327-1-git-send-email-dsa-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
2016-01-04 17:58 ` Tejun Heo
2016-01-04 18:53 ` David Ahern
[not found] ` <568ABFC3.3010803-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
2016-01-04 18:59 ` Tejun Heo
[not found] ` <20160104185936.GA3807-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-01-04 19:17 ` David Ahern
2016-01-04 19:23 ` Tejun Heo [this message]
2016-01-04 19:59 ` David Ahern
[not found] ` <568ACF13.3030007-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
2016-01-04 20:05 ` Tejun Heo
[not found] ` <20160104200518.GD3807-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-01-19 16:03 ` Stephen Hemminger
2016-01-19 16:06 ` David Ahern
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=20160104192301.GC3807@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=shm@cumulusnetworks.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).