From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Codel] coping with memory limitations and packet flooding in codel and fq_codel
Date: Mon, 27 Aug 2012 04:37:05 -0700 [thread overview]
Message-ID: <1346067425.2420.167.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw7XKwRtESqfiXsrkznoX2KRCkoHZifyjHMtZTJV1Yhzqg@mail.gmail.com>
On Sun, 2012-08-26 at 14:36 -0700, Dave Taht wrote:
> From looking over the history of this idea, it does seem to be a good
> idea for small devices with potentially big queues.
>
> http://www.spinics.net/lists/netdev/msg176967.html
>
> That said I do tend to agree with davem's summary in fixing the
> wifi drivers in the first place. The current allocation in the ath9k driver
> doesn't make any sense in the first place, which (to me) implies magic
> lies underneath that I'm reluctant to fiddle with, without deep knowledge
> of how the ath9k driver behaves with wep/wpa/ampdus, etc.
>
Problem is some hardware cannot do this in a smart way, without paying
the price of a sometime expensive copy.
Thats why I refined this idea to actually trigger only if current
memory needs are above a threshold.
If packets are received and immediately consumed, without potentially
staying a long time in a queue, it doesnt really matter they use 200 or
400% more ram than the rightly sized packets.
next prev parent reply other threads:[~2012-08-27 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 21:05 Dave Taht
2012-08-21 8:38 ` Eric Dumazet
2012-08-21 10:27 ` Andrew McGregor
2012-08-21 10:50 ` Eric Dumazet
2012-08-26 21:36 ` Dave Taht
2012-08-27 11:37 ` Eric Dumazet [this message]
2012-08-27 15:12 ` 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1346067425.2420.167.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nbd@nbd.name \
/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