From: jamal <hadi@cyberus.ca>
To: Tom Herbert <therbert@google.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/9] bql: Byte Queue Limits
Date: Thu, 25 Aug 2011 16:23:07 -0400 [thread overview]
Message-ID: <1314303787.2329.1.camel@mojatatu> (raw)
In-Reply-To: <CA+mtBx8mb0pAqVH19WK=e9LuLeyvnNTybROOURD2Rg6UtYe+bw@mail.gmail.com>
On Thu, 2011-08-25 at 08:29 -0700, Tom Herbert wrote:
> BQL is dynamic, and will increase the queue limit more aggressively
> than decrease it. So for instance, we can track the largest queue
> needed over 30 seconds which should be stable in the presence even in
> the presence of fluctuating bandwidth. The thing that worries me is
> rather the HW queues conform to the queue characteristics described in
> the patch. If transmit completions are random and not regular, BQL
> probably can't function well.
>
I think thats the challenge ;-> I wouldnt say it is random, but if my
understanding is correct the effect is a factor of number of stations
etc.
> If you'd like to bring this up on some wireless devices that would be
> great, I don't have easy access to any right now, but I can try to
> help otherwise.
I am most curious as well...
cheers,
jamal
next prev parent reply other threads:[~2011-08-25 20:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 4:43 [RFC PATCH v2 0/9] bql: Byte Queue Limits Tom Herbert
2011-08-08 13:06 ` jamal
2011-08-08 13:18 ` Johannes Berg
2011-08-25 15:29 ` Tom Herbert
2011-08-25 20:23 ` jamal [this message]
2011-08-25 15:19 ` Tom Herbert
2011-08-08 15:40 ` Stephen Hemminger
2011-08-08 17:51 ` Tom Herbert
2011-08-08 17:55 ` Stephen Hemminger
2011-08-08 17:56 ` Tom Herbert
2011-08-08 18:01 ` Tom Herbert
2011-08-08 18:19 ` Stephen Hemminger
2011-08-09 7:41 ` David Miller
2011-08-09 8:06 ` Eric Dumazet
2011-08-09 14:54 ` Stephen Hemminger
2011-08-09 18:28 ` Tom Herbert
2011-08-12 18:20 ` Stephen Hemminger
2011-08-13 0:33 ` Tom Herbert
2011-08-13 0:38 ` Stephen Hemminger
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=1314303787.2329.1.camel@mojatatu \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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;
as well as URLs for NNTP newsgroup(s).