From: Sam Leffler <sam@errno.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Ron Rindjunsky <ron.rindjunsky@intel.com>,
Nick Kossifidis <mickflemm@gmail.com>,
Michael Renzmann <mrenzmann@madwifi.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
bruno randolf <br1@einfach.org>
Subject: Re: implementing APSD?
Date: Wed, 20 Feb 2008 10:52:44 -0800 [thread overview]
Message-ID: <47BC76FC.7070109@errno.com> (raw)
In-Reply-To: <1ba2fa240802201043v1bd4fbddsc55c2230eb2a1480@mail.gmail.com>
Tomas Winkler wrote:
> On Feb 20, 2008 5:24 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
>
>> Hi,
>>
>> I've long thought about implementing APSD but it seems to require
>> setting the "more data" bit in an ACK frame and various other things.
>> Ron, I think you're the QoS expert, is that really how APSD works? If
>> so, does iwl firmware implement that?
>>
>
> We have uAPSD implementation, mainly AP part, yet again it for older
> mac. It will take a bit time to merge it in
> It's a mandatory feature for HT AP.
>
Really? Can you point where that's called out in the spec?
>
>> Also, does Atheros hardware implement that, and how? It doesn't look
>> like Broadcom firmware implements it, and I don't really understand how
>> one could implement it without many hardware queues, since it seems
>> timing critical to send out the frames to the station that is using
>> APSD.
>>
>>
> Don't believe it's possible to that without HW support.
>
Sorry, this is incorrect; you can do UAPSD w/o any special h/w support.
Sam
next prev parent reply other threads:[~2008-02-20 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:24 implementing APSD? Johannes Berg
2008-02-20 18:43 ` Tomas Winkler
2008-02-20 18:52 ` Sam Leffler [this message]
2008-02-20 18:56 ` Johannes Berg
2008-02-20 23:11 ` Guy Cohen
2008-02-20 23:52 ` Sam Leffler
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=47BC76FC.7070109@errno.com \
--to=sam@errno.com \
--cc=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
--cc=mrenzmann@madwifi.org \
--cc=ron.rindjunsky@intel.com \
--cc=tomasw@gmail.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).