From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ron Rindjunsky <ron.rindjunsky@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Jouni Malinen <j@w1.fi>, Tomas Winkler <tomasw@gmail.com>,
Patrick McHardy <kaber@trash.net>
Subject: Re: mac80211 QoS/aggregation questions, thoughts
Date: Fri, 1 Feb 2008 23:54:02 +0100 [thread overview]
Message-ID: <200802012354.02903.IvDoorn@gmail.com> (raw)
In-Reply-To: <1201904975.4188.88.camel@johannes.berg>
Hi,
> > All patches are currently in testing, and I hope to send them to wireless-2.6
> > next weekend.
>
> Ah cool, I'll hold off on doing anything then until then.
>
> > rt2400pci, rt2500pci and rt2500usb have a special dedicated queue which is called
> > the ATIM queue. The implementation is a guess since it was never used in the
> > legacy drivers. But it is clear it contains frames which are send directly after the beacon.
>
> Well I'd guess this is for the ATIM window. Broadcom firmware actually
> has an ATIM queue *and* a broadcast/multicast queue, I would expect that
> you should actually put broadcast/multicast traffic onto the beacon
> queue (unless the beacon queue only sends one packet per beacon
> interval)
In all Ralink drivers the beacon queue will only send out the frame each interval,
where rt2400pci and rt2500pci a interrupt will be triggered to request a new
beacon frame.
> ATIM is actually one of the things I haven't fully understood yet, see
> IEEE 802.11 11.2.2.
>
> > > 4. remove IEEE80211_TX_QUEUE_SVP, it's something strange and
> > > atheros specific
> >
> > I always wondered what the queue was. ;)
>
> spectralink voice protocol. I have not even the slightest clue.
>
> > HCCA queue is a big mysterie, there are registers to initialize it inside the device,
> > but in implementation of the legacy driver the queue was unused, I haven't found a
> > correct entry point yet to send frames over it, since that interface seems to be missing
> > in the device... So either I am missing something or the queue was half-implemented
> > in the device itself.. :S
>
> No idea, that's HCF (802.11e) stuff. Maybe they just never got around to
> finishing that implementation.
Or the documenation is just missing. ;)
In any case it will remain unused for rt61pci and rt73usb. I have seen some other
queue handling in the legacy rt2800 drivers but that driver needs more investigation
before I can say anything usefull about it.
Ivo
next prev parent reply other threads:[~2008-02-01 22:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 16:15 mac80211 QoS/aggregation questions, thoughts Johannes Berg
2008-02-01 21:43 ` Johannes Berg
2008-02-01 22:25 ` Ivo van Doorn
2008-02-01 22:32 ` Johannes Berg
2008-02-01 23:00 ` Ivo van Doorn
2008-02-01 23:24 ` Tomas Winkler
2008-02-01 23:30 ` Johannes Berg
2008-02-01 23:31 ` Ivo van Doorn
2008-02-03 15:36 ` Guy Cohen
2008-02-03 15:54 ` Ivo van Doorn
2008-02-01 22:16 ` Ivo van Doorn
2008-02-01 22:29 ` Johannes Berg
2008-02-01 22:54 ` Ivo van Doorn [this message]
2008-02-02 2:40 ` Nick Kossifidis
2008-02-02 7:21 ` Johannes Berg
2008-02-03 17:42 ` Jouni Malinen
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=200802012354.02903.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.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).