From: Thomas Graf <tgraf@suug.ch>
To: Ranjit Manomohan <ranjitm@google.com>
Cc: David Miller <davem@davemloft.net>,
kaber@trash.net, akpm@linux-foundation.org, lizf@cn.fujitsu.com,
menage@google.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Traffic control cgroups subsystem
Date: Thu, 11 Sep 2008 01:52:50 +0200 [thread overview]
Message-ID: <20080910235250.GL20815@postel.suug.ch> (raw)
In-Reply-To: <166fe7950809101637o1bf22869g4939707a35a3c93b@mail.gmail.com>
* Ranjit Manomohan <ranjitm@google.com> 2008-09-10 16:37
> Could you elaborate on the failure cases? We have found this to be
> useful in practice to prevent applications from reading large amounts
> of data off the network so it would be nice if it were supported.
It works fairly well for a small number of bulk streams when no packets
need to be dropped. The results get very inaccurate for higher number
of smaller streams when packets start getting dropped. The problem is
simply that currently none of the congestion notification mechanism
work in (internet) practice.
Therefore I think that it is not worth the effort. If you think
diffrently, I will be more than glad to review code. So far I haven't
seen anything that would work on ingress.
next prev parent reply other threads:[~2008-09-10 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 17:40 [PATCH 0/2] Traffic control cgroups subsystem Ranjit Manomohan
2008-09-10 20:22 ` David Miller
2008-09-10 20:44 ` Ranjit Manomohan
2008-09-10 22:12 ` Thomas Graf
2008-09-10 23:37 ` Ranjit Manomohan
2008-09-10 23:52 ` Thomas Graf [this message]
-- 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=20080910235250.GL20815@postel.suug.ch \
--to=tgraf@suug.ch \
--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=ranjitm@google.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