Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: bloat-devel@lists.bufferbloat.net
Subject: Re: Enabling Byte Queue Limits in the ath5k wireless driver
Date: Sat, 05 Oct 2013 20:39:59 -0700	[thread overview]
Message-ID: <5250DB8F.4060004@superduper.net> (raw)
In-Reply-To: <CAMdC6xak3DuBgfPuZe-idVx3gP2OruTjN7X9fsV_wfJtY6CbpQ@mail.gmail.com>

BQL does make sense, but TQL would be even better - 'Time Queue Limits'. 
Which would work based on an estimate of how much time each packet will 
take to send, and limiting the hardware queue to contain a total mount 
of 'time'. The purpose of the hardware queue is to mask interrupt and 
other latencies involved in refilling an empty queue - a time based 
phenomenon. Hence time is the best metric to control it - with fixed 
speed interfaced like ethernet bytes=time, but not so on wireless.

Simon

On 10/3/2013 11:49 AM, Anirudh Sivaraman wrote:
> Hi,
>
> I am looking into enabling BQL for the ath5k driver, and was wondering
> if anyone here knows of any prior efforts in this direction. In
> particular, is BQL even a sensible strategy for wireless drivers?
> Thank you in advance for any advice you may have in this regard.
>
> Anirudh
> _______________________________________________
> Bloat-devel mailing list
> Bloat-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat-devel


  reply	other threads:[~2013-10-06  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 18:49 Anirudh Sivaraman
2013-10-06  3:39 ` Simon Barber [this message]
2013-10-06 13:31   ` Anirudh Sivaraman
2013-10-06 15:01     ` Simon Barber
2013-10-06 16:36       ` Anirudh Sivaraman
2013-10-06 21:03         ` Simon Barber
2013-10-08 11:00           ` Anirudh Sivaraman

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=5250DB8F.4060004@superduper.net \
    --to=simon@superduper.net \
    --cc=bloat-devel@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