From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Thomas Pedersen <thomas@cozybit.com>,
devel@lists.open80211s.org, linux-wireless@vger.kernel.org,
jlopex@gmail.com
Subject: Re: [PATCH 0/2] QoS headers for mesh
Date: Wed, 07 Sep 2011 20:08:40 +0200 [thread overview]
Message-ID: <1315418920.4002.13.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1315347976-13950-1-git-send-email-javier@cozybit.com> (sfid-20110907_002659_987760_30CFF5E1)
On Tue, 2011-09-06 at 15:26 -0700, Javier Cardona wrote:
> Mesh frames are required to have QoS headers to indicate the presence of a Mesh
> Control Header in the payload. These patches add QoS headers to mesh frames,
> but note that they don't implement full QoS support: mesh stations don't
> currently advertise QoS capabilities.
Uh, so does mesh want full QoS support or just QoS headers? The latter
seems a little odd to me. But if it wants QoS how about zd1211rw? I
don't think that even supports QoS?
That's one thing that bothers me a little bit about this patchset --
previously, QoS frames could only happen when the device actually
supported 4 queues, now this rule seems to be broken. I don't expect
this to be a major issue, but it certainly is unexpected and will
probably be forgotten by a lot of people in the future ...
johannes
next prev parent reply other threads:[~2011-09-07 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 22:26 [PATCH 0/2] QoS headers for mesh Javier Cardona
2011-09-06 22:26 ` [PATCH 1/2] mac80211: Start implementing QoS support for mesh interfaces Javier Cardona
2011-09-06 22:26 ` [PATCH 2/2] mac80211: Mesh data frames must have the QoS header Javier Cardona
2011-09-07 18:08 ` Johannes Berg [this message]
2011-09-07 18:14 ` [PATCH 0/2] QoS headers for mesh Johannes Berg
2011-09-07 18:36 ` Javier Cardona
2011-09-07 18:46 ` Johannes Berg
2011-09-08 3:34 ` Javier Cardona
2011-09-08 7:01 ` Johannes Berg
2011-09-07 18:23 ` Javier Cardona
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=1315418920.4002.13.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=jlopex@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=thomas@cozybit.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).