From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/1] mac80211: tear down all agg queues when restart/reconfig hw
Date: Tue, 02 Feb 2010 17:11:47 -0800 [thread overview]
Message-ID: <1265159507.15427.0.camel@wwguy-ubuntu> (raw)
In-Reply-To: <201002030209.38862.chunkeey@googlemail.com>
Good point, thanks
On Tue, 2010-02-02 at 17:09 -0800, Christian Lamparter wrote:
> On Wednesday 03 February 2010 01:52:50 wey-yi.w.guy@intel.com wrote:
> > From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> >
> > When there is a need to restart/reconfig hw, tear down all the
> > aggregation queues and let the mac80211 and driver get in-sync and have
> > the opportunity to re-establish the aggregation queues.
> >
> > Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> > ---
> > net/mac80211/util.c | 5 +++++
> > 1 files changed, 5 insertions(+), 0 deletions(-)
> >
> > diff --git a/net/mac80211/util.c b/net/mac80211/util.c
> > index ca170b4..6116ad0 100644
> > --- a/net/mac80211/util.c
> > +++ b/net/mac80211/util.c
> > @@ -1188,6 +1188,11 @@ int ieee80211_reconfig(struct ieee80211_local *local)
> > ieee80211_wake_queues_by_reason(hw,
> > IEEE80211_QUEUE_STOP_REASON_SUSPEND);
> >
> > + if (hw->flags & IEEE80211_HW_AMPDU_AGGREGATION) {
> > + list_for_each_entry_rcu(sta, &local->sta_list, list) {
> > + ieee80211_sta_tear_down_BA_sessions(sta);
> > + }
> > + }
> hmm, I somehow miss the rcu_read_lock(); and rcu_read_unlock(); around
> list_for_each_entry_rcu... Are you really sure that you don't need
> them?
>
> Regards,
> Chr
prev parent reply other threads:[~2010-02-03 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 0:52 [PATCH 1/1] mac80211: tear down all agg queues when restart/reconfig hw wey-yi.w.guy
2010-02-03 1:09 ` Christian Lamparter
2010-02-03 1:11 ` Guy, Wey-Yi [this message]
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=1265159507.15427.0.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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