From: "Ranjit Manomohan" <ranjitm@google.com>
To: "David Miller" <davem@davemloft.net>
Cc: kaber@trash.net, akpm@linux-foundation.org, lizf@cn.fujitsu.com,
menage@google.com, tgraf@suug.ch, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Traffic control cgroups subsystem
Date: Wed, 10 Sep 2008 13:44:23 -0700 [thread overview]
Message-ID: <166fe7950809101344l7a5e2b7pfba8b2a7c03814a1@mail.gmail.com> (raw)
In-Reply-To: <20080910.132251.73509521.davem@davemloft.net>
On Wed, Sep 10, 2008 at 1:22 PM, David Miller <davem@davemloft.net> wrote:
>
> I definitely prefer Thomas Graf's work, this stuff is very ugly
> and way overengineered.
>
Could you be more specific? Thomas' work is almost identical to this
(except that he does not store the cgroup id into the socket which is
a trivial change which has downsides which I have pointed out).
Additionally this approach has only minor modifications to the core
networking stack. What portions do you consider ugly and over
engineered and what alternative implementations would you prefer?
Please see the follow up I have sent to Thomas' proposal about why we
need this design approach to handle the inbound case.
I'd be ok if you accepted either change since we just want a standard
kernel mechanism to do this.
-Thanks,
Ranjit
> So no, I won't consider for net-next-2.6, sorry.
>
>
next prev parent reply other threads:[~2008-09-10 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 17:40 Ranjit Manomohan
2008-09-10 20:22 ` David Miller
2008-09-10 20:44 ` Ranjit Manomohan [this message]
2008-09-10 22:12 ` Thomas Graf
2008-09-10 23:37 ` Ranjit Manomohan
2008-09-10 23:52 ` Thomas Graf
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 6:16 김재열
2008-09-26 9:57 ` Chen Zumeng
2008-10-15 13:03 ` Chen Zumeng
2008-09-26 1:07 김재열
2008-08-22 0:53 Ranjit Manomohan
2008-07-18 21:25 Ranjit Manomohan
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=166fe7950809101344l7a5e2b7pfba8b2a7c03814a1@mail.gmail.com \
--to=ranjitm@google.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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
all inboxes | Powered by JetHome®