All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 08 Sep 2011 09:01:31 +0200	[thread overview]
Message-ID: <1315465291.3948.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAPjQAd8su+CLkq84L2xtZO3XrKv2RS3fehsYVu2T_5MRwbnQxg@mail.gmail.com> (sfid-20110908_053518_772793_714755F5)

On Wed, 2011-09-07 at 20:34 -0700, Javier Cardona wrote:

> Kazuyuki Sakoda, the current technical editor of TGs kindly pointed me
> to the right section in the draft:  Sec 5.2.14.3 states that "mesh
> STAs are QoS STAs (...) [that] implement a subset of QoS
> functionality".  The use of the QoS frame format and EDCA support are
> mandatory.

Makes sense.

> Based on that I'd like to prevent the creation of mesh interfaces on
> phy's that don't support multiple queues.  Would you like to suggest a
> good place to perform that check?

Since we probably can't do that in cfg80211, the most logical place
would be ieee80211_check_concurrent_iface() even though on the face of
it that function does something else; however, note the comment on
ieee80211_do_open(). Maybe it warrants a rename of the function,
something like ieee80211_check_iface_possible() maybe?

johannes


  reply	other threads:[~2011-09-08  7:01 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 ` [PATCH 0/2] QoS headers for mesh Johannes Berg
2011-09-07 18:14   ` 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 [this message]
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=1315465291.3948.3.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.