From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
bcm43xx-dev@lists.berlios.de, Jiri Benc <jbenc@suse.cz>,
linux-wireless@vger.kernel.org, Joseph Jezak <josejx@gentoo.org>
Subject: Re: [RFC PATCH] bcm43xx QoS support
Date: Sun, 17 Jun 2007 11:10:44 +0200 [thread overview]
Message-ID: <1182071444.23681.14.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240706161630r1fdb2ac1m87039a088c7d6bfd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
On Sun, 2007-06-17 at 02:30 +0300, Tomas Winkler wrote:
> > > There is also a discussion about supporting hardware queues in qdisc
> > > in netdev.
> >
> > Which isn't really a concern to the driver since only mac80211 will need
> > to be changed for that.
> >
> I'm not sure it's only mac80211 problem as driver is responsible for
> stopping and waking up the queues. Only driver knows whether hw queue
> is full or not.
Of course, but we already have that API in mac80211, hence well-written
drivers already tell mac80211 about it so all we'd need to do is change
mac80211 to tell the net layer :)
> > I suppose the question is: what are we missing in mac80211 now? It seems
> > that we have no way of sending out QoS-data frames and that seems weird..
>
> QoS frame are send just fine by mac80211 (at least under iwlwifi),
> only the sequence numbers has to be overwritten in driver since the
> current handler doesn't advance them per TID.
Oh, you're right, I missed that wme_qdiscop_enqueue does that.
> > Nor do we parse TXOP information etc. Possibly this is because we
> > support WME and that's based on an early 802.11e draft?
>
> I addition wme.c qdisc scheduler is rather naive one, it only
> statically assign priorities, it wouldn't pass WMM certification I
> guess.
I have no idea what WMM certification contains. All I've been trying to
say is that this area really needs some work to be useful.
For the problem at hand, namely some QoS support in bcm43xx, we'll just
have to hardcode some QoS parameters for now, I'd think, but I don't
know what those would be.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-06-17 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 11:28 [RFC PATCH] bcm43xx QoS support Michael Buesch
2007-06-16 21:38 ` Tomas Winkler
2007-06-16 22:17 ` Johannes Berg
2007-06-16 23:30 ` Tomas Winkler
2007-06-17 9:10 ` Johannes Berg [this message]
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=1182071444.23681.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jbenc@suse.cz \
--cc=josejx@gentoo.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--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).