From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"Dave Taht" <dave.taht@gmail.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [PATCH net-next v6] Add Common Applications Kept Enhanced (cake) qdisc
Date: Tue, 1 May 2018 12:12:45 -0700 [thread overview]
Message-ID: <4ec8da81-8671-f434-bada-27088b09ce7b@gmail.com> (raw)
In-Reply-To: <878t932ont.fsf@toke.dk>
On 05/01/2018 11:53 AM, Toke Høiland-Jørgensen wrote:
> *sigh* - can do, I guess. Though I'm not sure what that is going to
> accomplish, exactly?
I guess that nobody really wants to really review Cake if
it is a file with 2700 lines of code and hundreds of variables/tunables.
Sure, we have big files in networking land, as a result of thousands of changes.
If you split it, then maybe the work can be split among reviewers as a result.
Or maybe David Miller can simply merge your patch as is, and hope for the best,
I really do not know.
It seems you guys spent years/months on work on this stuff, so what is the big deal
about presenting your work in the best possible way ?
Thanks.
next prev parent reply other threads:[~2018-05-01 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 21:34 Toke Høiland-Jørgensen
2018-04-30 21:21 ` Cong Wang
2018-04-30 21:27 ` Dave Taht
2018-04-30 23:04 ` Cong Wang
2018-05-01 11:36 ` Toke Høiland-Jørgensen
2018-05-01 16:06 ` Eric Dumazet
2018-05-01 18:31 ` Jonathan Morton
2018-05-01 18:53 ` Toke Høiland-Jørgensen
2018-05-01 19:12 ` Eric Dumazet [this message]
2018-05-01 19:14 ` David Miller
2018-05-01 19:31 ` Toke Høiland-Jørgensen
2018-05-01 19:41 ` Eric Dumazet
2018-05-01 21:54 ` Toke Høiland-Jørgensen
2018-05-01 22:31 ` Cong Wang
2018-05-01 19:22 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ec8da81-8671-f434-bada-27088b09ce7b@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=toke@toke.dk \
--cc=xiyou.wangcong@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