From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Guy Cohen" <guy@cguy.net>
Cc: "Tomas Winkler" <tomasw@gmail.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Ron Rindjunsky" <ron.rindjunsky@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Jouni Malinen" <j@w1.fi>, "Patrick McHardy" <kaber@trash.net>
Subject: Re: mac80211 QoS/aggregation questions, thoughts
Date: Sun, 3 Feb 2008 16:54:54 +0100 [thread overview]
Message-ID: <200802031654.54311.IvDoorn@gmail.com> (raw)
In-Reply-To: <247d6d340802030736t4a51c4bcg92130277f84e1b58@mail.gmail.com>
On Sunday 03 February 2008, Guy Cohen wrote:
> On 2/2/08, Ivo van Doorn <ivdoorn@gmail.com> wrote:
> > On Saturday 02 February 2008, Tomas Winkler wrote:
> > > 4965 has 4 queues which are used for regular WMM. Only 11 queues
> > > might be used for aggregation, but in AP mode we might map one of the
> > > queues to after beacon multicast traffic.
> >
> > Just out of interest, and I don't know about the iwl4965 driver specifics,
> > but how will you make sure those frames are send after the beacon?
> > Does the beacon trigger an interrupt after each interval which allows you to queue
> > the frames or is some other approach used?
>
> For iwl4965, mcast frames are queued into a separate HW TX FIFO (no
> need to buffer at the host). Beacon periodic transmission and
> controling the TX of mcast frames from the mcast FIFO are all timely
> done in real-time by the device.
Thanks for the explanation.
Ivo
next prev parent reply other threads:[~2008-02-03 15:55 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 [this message]
2008-02-01 22:16 ` Ivo van Doorn
2008-02-01 22:29 ` Johannes Berg
2008-02-01 22:54 ` Ivo van Doorn
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=200802031654.54311.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=guy@cguy.net \
--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).