From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: bismark-devel@projectbismark.net,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
Srikanth Sundaresan <srikanth@gatech.edu>
Subject: Re: some (less than funny) interactions with networking on openwrt (and other systems)
Date: Wed, 27 Jul 2011 20:57:06 +0200 [thread overview]
Message-ID: <7itya7eem5.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <CAA93jw5s6_8uhR9t7N+XcWhQKbp9GjNJS7wYL5dt-xj0Wm85ww@mail.gmail.com> (Dave Taht's message of "Wed, 27 Jul 2011 12:36:50 -0600")
>> > 2) qos-scripts (already mentioned) as an additional problem of always
>> > ending up with 127 buckets or so for packets in the SFQ qdisc, when a
>> > 'righter' number would be closer to 8-32.
>>
>> Huh?
>>
>
> Tc reports 127 for SFQ with the default qdisc
I mean -- having fewer buckets than that doesn't make any sense to me,
since you're going to have massive hash collisions.
-- Juliusz
prev parent reply other threads:[~2011-07-27 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 21:54 Dave Taht
2011-07-27 15:46 ` Juliusz Chroboczek
2011-07-27 18:36 ` Dave Taht
2011-07-27 18:57 ` Juliusz Chroboczek [this message]
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=7itya7eem5.fsf@lanthane.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=bismark-devel@projectbismark.net \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=srikanth@gatech.edu \
/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