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 v2 1/3] mac80211: Start implementing QoS support for mesh interfaces
Date: Fri, 09 Sep 2011 10:02:18 +0200 [thread overview]
Message-ID: <1315555338.17050.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAPjQAd9+QB2WpovrrLV3ArPRqv-tEY_HY3tKjYjvFcJZxM=LHg@mail.gmail.com> (sfid-20110908_181929_199296_563197DA)
On Thu, 2011-09-08 at 09:17 -0700, Javier Cardona wrote:
> On Thu, Sep 8, 2011 at 12:01 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Wed, 2011-09-07 at 17:49 -0700, Javier Cardona wrote:
> >
> >> + /* For mesh, the use of the QoS header is mandatory */
> >> + if (ieee80211_vif_is_mesh(&sdata->vif))
> >> + sta_flags |= WLAN_STA_WME;
> >> +
> >
> > With patch 3, this piece seems unnecessary?
>
> At that point we don't know who the next hop peer will so the previous
> block (below) will not find an sta. Also, we want the QoS header in
> multicast frames. So I thought this might be the least intrusive way.
>
> >>>
> if (!is_multicast_ether_addr(hdr.addr1)) {
> rcu_read_lock();
> sta = sta_info_get(sdata, hdr.addr1);
> if (sta)
> sta_flags = get_sta_flags(sta);
> rcu_read_unlock();
> }
> >>>
Ok, yeah, that makes sense.
johannes
next prev parent reply other threads:[~2011-09-09 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 0:49 [PATCH v2 0/3] QoS headers for mesh Javier Cardona
2011-09-08 0:49 ` [PATCH v2 1/3] mac80211: Start implementing QoS support for mesh interfaces Javier Cardona
2011-09-08 7:01 ` Johannes Berg
2011-09-08 16:17 ` Javier Cardona
2011-09-09 8:02 ` Johannes Berg [this message]
2011-09-08 0:49 ` [PATCH v2 2/3] mac80211: Mesh data frames must have the QoS header Javier Cardona
2011-09-08 0:49 ` [PATCH v2 3/3] mac80211: Mark all mesh stations as QoS capable 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=1315555338.17050.1.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).