From: Patrick McHardy <kaber@trash.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Ron Rindjunsky <ron.rindjunsky@intel.com>,
linville@tuxdriver.com, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org, flamingice@sourmilk.net,
yi.zhu@intel.com
Subject: Re: [RFC PATCH 06/10] mac80211: A-MPDU Tx adding qdisc support
Date: Mon, 28 Jan 2008 14:44:36 +0100 [thread overview]
Message-ID: <479DDC44.4050600@trash.net> (raw)
In-Reply-To: <1ba2fa240801271119m29a316eeib815facfbf2051e0@mail.gmail.com>
Tomas Winkler wrote:
> On Jan 27, 2008 7:55 PM, Patrick McHardy <kaber@trash.net> wrote:
>
>> Is there a reason to add new features to this instead of using
>> the generic multiqueue support, moving classification to a
>> classifier and killing wme?
>>
> Multiqueue is where we are heading to. We have developed this solution
> before multiqueue was accepted and it worked well for few months
> already so it can provide enough usability for 11n users for now.
> We still have too many opens to close so we prefer to stage them
> rather then choke on them. It will take few more weeks till we start
> to work on it unless someone else take the lead of course.
Thanks for the explanation.
next prev parent reply other threads:[~2008-01-28 14:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 17:22 [RFC PATCH 0/10] mac80211/iwlwifi: A-MPDU Tx support Ron Rindjunsky
2008-01-10 17:22 ` [RFC PATCH 01/10] mac80211: A-MPDU Tx add session's and low level driver's API Ron Rindjunsky
2008-01-11 16:29 ` Johannes Berg
2008-01-13 15:17 ` Ron Rindjunsky
2008-01-13 21:58 ` Johannes Berg
2008-01-14 9:25 ` Ron Rindjunsky
2008-01-10 17:22 ` [RFC PATCH 02/10] mac80211: A-MPDU Tx add MLME structures Ron Rindjunsky
2008-01-11 16:31 ` Johannes Berg
2008-01-10 17:22 ` [RFC PATCH 03/10] mac80211: A-MPDU Tx adding basic functionality Ron Rindjunsky
2008-01-11 16:51 ` Johannes Berg
2008-01-13 15:18 ` Ron Rindjunsky
2008-01-13 21:51 ` Johannes Berg
2008-01-14 9:26 ` Ron Rindjunsky
2008-01-14 10:35 ` Johannes Berg
2008-01-10 17:22 ` [RFC PATCH 04/10] mac80211: A-MPDU Tx MLME data initialization Ron Rindjunsky
2008-01-10 17:22 ` [RFC PATCH 05/10] mac80211: A-MPDU add debugfs support Ron Rindjunsky
2008-01-10 17:22 ` [RFC PATCH 06/10] mac80211: A-MPDU Tx adding qdisc support Ron Rindjunsky
2008-01-11 16:55 ` Johannes Berg
2008-01-27 17:55 ` Patrick McHardy
2008-01-27 19:19 ` Tomas Winkler
2008-01-28 13:44 ` Patrick McHardy [this message]
2008-01-10 17:22 ` [RFC PATCH 07/10] mac80211: A-MPDU Tx change tx_status to support Block Ack data Ron Rindjunsky
2008-01-11 16:56 ` Johannes Berg
2008-01-12 11:43 ` Tomas Winkler
[not found] ` <49299.::ffff:91.5.126.126.1200138845.squirrel@secure.sipsolutions.net>
2008-01-12 12:37 ` Rindjunsky, Ron
[not found] ` <-2543242200241674408@unknownmsgid>
2008-01-12 12:47 ` Tomas Winkler
2008-01-10 17:22 ` [RFC PATCH 08/10] iwlwifi: A-MPDU Tx conform API to mac80211 Ron Rindjunsky
2008-01-10 17:22 ` [RFC PATCH 09/10] iwlwifi: A-MPDU Tx conform flows " Ron Rindjunsky
2008-01-10 17:22 ` [RFC PATCH 10/10] iwlwifi: A-MPDU Tx conform block Ack rate scaling " Ron Rindjunsky
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=479DDC44.4050600@trash.net \
--to=kaber@trash.net \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ron.rindjunsky@intel.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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).