linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "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: Sat, 2 Feb 2008 00:31:24 +0100	[thread overview]
Message-ID: <200802020031.24532.IvDoorn@gmail.com> (raw)
In-Reply-To: <1ba2fa240802011524g38a9583fs7c4b792bda844327@mail.gmail.com>

On Saturday 02 February 2008, Tomas Winkler wrote:
> On Feb 1, 2008 11:43 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > Any thoughts on this patch? The only thing it should really actually
> > change is removing the IBSS beacon queue configuration, but as I've
> > explained previously that really has to be done by the driver because we
> > don't know whether the driver even uses queues for beaconing... Also we
> > never reset that info.
> >
> > Also, I'm wondering, iwl4965 has 16 queues, can it use 4 for regular WMM
> > and the other 12 for aggregation? And how does it configure the access
> > parameters for aggregation? I don't see conf_tx() calls anywhere for
> > that.
> >
> 
> 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?

I am asking because I am not sure how I should implement such a thing for
the rt2x00 drivers that don't have a device ATIM queue (which automatically
sends the frames after the beacon was send).

> One queue is reserved for communicating with FW.  The number my differ
> on further NICs.
> 
> All the traffic queues 4 WMM + 11 AGG are served according regular WMM
> policy, 4 AC - these are configured by conf_tx.  The aggregation
> queues are needed for handling ordering of frames correctly and not
> for on media prioritizing
> 
> Sorry but I have to review your patch later
> Thanks
> Tomas


  parent reply	other threads:[~2008-02-01 23:31 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 [this message]
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
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=200802020031.24532.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).