From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Adrian Popescu <adriannnpopescu@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Dropping dropped
Date: Fri, 15 Feb 2019 11:55:59 +0100 [thread overview]
Message-ID: <87r2c9s4lc.fsf@toke.dk> (raw)
In-Reply-To: <CAF3M4P1J_iMrPGeotx3_y9LnMbMRVLa0b2T6CD5YvoncoO7q=w@mail.gmail.com>
Adrian Popescu <adriannnpopescu@gmail.com> writes:
> On Thu, Feb 14, 2019 at 4:35 PM Toke Høiland-Jørgensen <toke@redhat.com>
> wrote:
>
>> Adrian Popescu <adriannnpopescu@gmail.com> writes:
>>
>> > Hello,
>> >
>> > I've taken a look at cake's source code to see what simple changes could
>> be
>> > made to attempt to speed it up. There seemed to be a per flow variable
>> > called dropped which might not be that useful for regular users. The
>> > attached patch removes it.
>>
>> I appreciate the sentiment; however, we keep a lot of statistics for a
>> reason, and we don't want to just drop those. Besides, a single variable
>> increment is probably not going to make much difference for performance.
>>
>
> Perhaps this seemed I implied that it was more than an experiment or
> something meant to be merged. Is sharing a patch to start a conversation
> frowned upon?
Not at all. Just pointing out why this particular approach is probably
not going to get you that far :)
> The point is that low end routers can't run cake at high speeds. It
> doesn't make sense to buy more expensive hardware for home networks.
Yeah, I'm aware of the issue. However, I'm not too hopeful that it will
be possible to squeeze significantly more performance out of the old
hardware, sadly. I'd love to be proven wrong, though!
-Toke
next prev parent reply other threads:[~2019-02-15 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 14:01 Adrian Popescu
2019-02-14 14:35 ` Toke Høiland-Jørgensen
2019-02-15 8:23 ` Adrian Popescu
2019-02-15 10:55 ` Toke Høiland-Jørgensen [this message]
2019-02-15 20:45 ` Dave Taht
2019-02-16 9:35 ` Adrian Popescu
2019-02-18 20:42 ` Adrian Popescu
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=87r2c9s4lc.fsf@toke.dk \
--to=toke@redhat.com \
--cc=adriannnpopescu@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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