From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: Friedrich.Beckmann@infineon.com, linux-wireless@vger.kernel.org, j@w1.fi
Subject: Re: iwlwifi aggregation info
Date: Wed, 30 Jul 2008 19:08:00 +0300 [thread overview]
Message-ID: <1ba2fa240807300908x5489e3f8g54ff83e7e5912c0b@mail.gmail.com> (raw)
In-Reply-To: <1217431179.10489.134.camel@johannes.berg>
On Wed, Jul 30, 2008 at 6:19 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Wed, 2008-07-30 at 16:59 +0300, Tomas Winkler wrote:
>
>> > Well qdiscs don't just do that, depending on the configuration, so we
>> > shouldn't rely on them doing just that.
>>
>> I know but this was the primary purpose of MQ to push the scheduling
>> decision to HW if I'm not mistaken.
>
> I thought it was more about the upper level locking, ethernet hw really
> just round-robins most of the time. Although it will, of course, be used
> for scheduling decisions.
>
> Is aggregation really a scheduling decision though?
>
>> We really don't need anything else just queueing.
>
> Exactly, but qdiscs do most definitely not provide just queueing, and we
> should not deprive the user of the ability to use qdiscs on wireless.
>
>> For example what the
>> prioritization which is done in current wme.c
>> is wrong and it won't pass certification and creates starvation.
>> Tested and proved.
>
> Can you explain how starvation happens? In what scenarios? With or
> without aggregation?
for (queue = 0; queue < QD_NUM(hw); queue++)
This always starts 0 prioritize dequeue the first frame. But what we
need is RR and let HW to prioritize the transmission according AC
Tomas
next prev parent reply other threads:[~2008-07-30 16:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 11:32 iwlwifi aggregation info Johannes Berg
2008-07-29 11:36 ` Johannes Berg
2008-07-29 12:25 ` Tomas Winkler
2008-07-29 12:27 ` Johannes Berg
2008-07-29 12:35 ` Tomas Winkler
2008-07-29 12:53 ` Johannes Berg
2008-07-29 13:04 ` Tomas Winkler
2008-07-29 13:07 ` Johannes Berg
2008-07-29 13:18 ` Tomas Winkler
2008-07-29 13:23 ` Johannes Berg
2008-07-29 13:43 ` Tomas Winkler
2008-07-29 13:46 ` Johannes Berg
2008-07-29 14:06 ` Tomas Winkler
2008-07-29 14:21 ` Johannes Berg
2008-07-29 15:55 ` Tomas Winkler
2008-07-30 9:53 ` Johannes Berg
2008-07-30 11:03 ` Friedrich.Beckmann
2008-07-30 13:19 ` Johannes Berg
2008-07-30 13:45 ` Tomas Winkler
2008-07-30 13:50 ` Johannes Berg
2008-07-30 13:59 ` Tomas Winkler
2008-07-30 15:19 ` Johannes Berg
2008-07-30 16:08 ` Tomas Winkler [this message]
2008-07-31 13:05 ` Johannes Berg
2008-07-31 18:14 ` Tomas Winkler
2008-07-31 18:23 ` Johannes Berg
2008-07-31 19:16 ` Tomas Winkler
2008-08-01 12:09 ` Johannes Berg
2008-08-01 12:40 ` Tomas Winkler
2008-08-01 12:54 ` Johannes Berg
2008-08-06 21:45 ` Johannes Berg
2008-08-06 22:05 ` Tomas Winkler
2008-08-06 22:31 ` Tomas Winkler
2008-08-07 11:13 ` mac80211 aggregation (was: iwlwifi aggregation info) Johannes Berg
2008-08-07 12:21 ` Friedrich.Beckmann
2008-08-07 12:31 ` Johannes Berg
2008-08-07 13:00 ` Friedrich.Beckmann
2008-07-30 12:01 ` iwlwifi aggregation info Tomas Winkler
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=1ba2fa240807300908x5489e3f8g54ff83e7e5912c0b@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=Friedrich.Beckmann@infineon.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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