From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v2 06/22] mac80211: pull mgmt frame rx into rx handler
Date: Thu, 10 Jun 2010 08:28:08 +0200 [thread overview]
Message-ID: <1276151288.3623.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <19472.26203.835523.525595@gargle.gargle.HOWL>
On Thu, 2010-06-10 at 09:43 +0530, Sujith wrote:
> Johannes Berg wrote:
> > -ieee80211_rx_result
> > -ieee80211_mesh_rx_mgmt(struct ieee80211_sub_if_data *sdata, struct sk_buff *skb)
> > -{
> > - struct ieee80211_local *local = sdata->local;
> > - struct ieee80211_mgmt *mgmt;
> > - u16 fc;
> > -
> > - if (skb->len < 24)
> > - return RX_DROP_MONITOR;
> > -
> > - mgmt = (struct ieee80211_mgmt *) skb->data;
> > - fc = le16_to_cpu(mgmt->frame_control);
> > -
> > - switch (fc & IEEE80211_FCTL_STYPE) {
> > - case IEEE80211_STYPE_ACTION:
> > - case IEEE80211_STYPE_PROBE_RESP:
> > - case IEEE80211_STYPE_BEACON:
> > - skb_queue_tail(&sdata->skb_queue, skb);
> > - ieee80211_queue_work(&local->hw, &sdata->work);
> > - return RX_QUEUED;
> > - }
> > -
> > - return RX_CONTINUE;
>
> Am not familiar with mesh code, but this changes the semantics, no ?
>
> > - if (ieee80211_vif_is_mesh(&sdata->vif))
> > - return ieee80211_mesh_rx_mgmt(sdata, rx->skb);
> > + stype = mgmt->frame_control & cpu_to_le16(IEEE80211_FCTL_STYPE);
> > +
> > + if (!ieee80211_vif_is_mesh(&sdata->vif) &&
> > + sdata->vif.type != NL80211_IFTYPE_ADHOC &&
> > + sdata->vif.type != NL80211_IFTYPE_STATION)
> > + return RX_DROP_MONITOR;
> >
> > - if (sdata->vif.type == NL80211_IFTYPE_ADHOC)
> > - return ieee80211_ibss_rx_mgmt(sdata, rx->skb);
> > + switch (stype) {
> > + case cpu_to_le16(IEEE80211_STYPE_BEACON):
> > + case cpu_to_le16(IEEE80211_STYPE_PROBE_RESP):
> > + /* process for all: mesh, mlme, ibss */
> > + break;
> > + case cpu_to_le16(IEEE80211_STYPE_DEAUTH):
> > + case cpu_to_le16(IEEE80211_STYPE_DISASSOC):
> > + /* process only for station */
> > + if (sdata->vif.type != NL80211_IFTYPE_STATION)
> > + return RX_DROP_MONITOR;
> > + break;
> > + case cpu_to_le16(IEEE80211_STYPE_PROBE_REQ):
> > + case cpu_to_le16(IEEE80211_STYPE_AUTH):
> > + /* process only for ibss */
> > + if (sdata->vif.type != NL80211_IFTYPE_ADHOC)
> > + return RX_DROP_MONITOR;
> > + break;
> > + default:
> > + return RX_DROP_MONITOR;
> > + }
> >
> > - if (sdata->vif.type == NL80211_IFTYPE_STATION)
> > - return ieee80211_sta_rx_mgmt(sdata, rx->skb);
> > + /* queue up frame and kick off work to process it */
> > + skb_queue_tail(&sdata->skb_queue, rx->skb);
> > + ieee80211_queue_work(&rx->local->hw, &sdata->work);
> >
> > - return RX_DROP_MONITOR;
> > + return RX_QUEUED;
> > }
>
> RX_QUEUED is the default return status for IBSS/Managed but mesh
> originally used RX_CONTINUE.
Mesh also used (and needed to!) RX_QUEUED for the case where it actually
wanted the packet. I just wrote the code the other way around -- before
it was returning RX_QUEUED if wanted, now it short-cuts to
"RX_DROP_MONITOR" if unwanted.
> Wouldn't this change mesh mode's existing behavior ?
No, I don't think it does, in ieee80211_rx_h_mgmt() RX_CONTINUE and
RX_DROP_MONITOR are equivalent since that's the last possible thing to
happen with a (management) frame. Unless I'm misunderstanding you?
johannes
next prev parent reply other threads:[~2010-06-10 6:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:01 [RFC v2 00/22] aggregation locking rework v2 Johannes Berg
2010-06-09 15:01 ` [RFC v2 01/22] mac80211: simplify station/aggregation code Johannes Berg
2010-06-09 15:01 ` [RFC v2 02/22] mac80211: use common skb queue Johannes Berg
2010-06-09 15:01 ` [RFC v2 03/22] mac80211: use common work struct Johannes Berg
2010-06-09 15:01 ` [RFC v2 04/22] mac80211: use common work function Johannes Berg
2010-06-09 15:01 ` [RFC v2 05/22] mac80211: common work skb freeing Johannes Berg
2010-06-09 15:01 ` [RFC v2 06/22] mac80211: pull mgmt frame rx into rx handler Johannes Berg
2010-06-10 4:13 ` Sujith
2010-06-10 6:28 ` Johannes Berg [this message]
2010-06-10 6:35 ` Sujith
2010-06-09 15:01 ` [RFC v2 07/22] mac80211: always process blockack action from workqueue Johannes Berg
2010-06-10 4:14 ` Sujith
2010-06-10 6:25 ` Johannes Berg
2010-06-09 15:01 ` [RFC v2 08/22] mac80211: move blockack stop due to fragmentation Johannes Berg
2010-06-09 15:01 ` [RFC v2 09/22] mac80211: move aggregation callback processing Johannes Berg
2010-06-09 15:01 ` [RFC v2 10/22] mac80211: use RCU for RX aggregation Johannes Berg
2010-06-09 15:01 ` [RFC v2 11/22] mac80211: use RCU for TX aggregation Johannes Berg
2010-06-09 15:01 ` [RFC v2 12/22] mac80211: remove non-irqsafe aggregation callbacks Johannes Berg
2010-06-09 15:01 ` [RFC v2 13/22] mac80211: refcount aggregation queue stop Johannes Berg
2010-06-09 15:01 ` [RFC v2 14/22] mac80211: make TX aggregation start/stop request async Johannes Berg
2010-06-09 15:01 ` [RFC v2 15/22] mac80211: move BA session work Johannes Berg
2010-06-09 15:01 ` [RFC v2 16/22] mac80211: defer RX agg session teardown to work Johannes Berg
2010-06-09 15:01 ` [RFC v2 17/22] mac80211: fix RX aggregation timer Johannes Berg
2010-06-09 15:02 ` [RFC v2 18/22] mac80211: change RX aggregation locking Johannes Berg
2010-06-09 15:02 ` [RFC v2 19/22] mac80211: defer TX agg session teardown to work Johannes Berg
2010-06-09 15:02 ` [RFC v2 20/22] mac80211: change TX aggregation locking Johannes Berg
2010-06-09 15:02 ` [RFC v2 21/22] mac80211: allow drivers to sleep in ampdu_action Johannes Berg
2010-06-09 15:02 ` [RFC v2 22/22] mac80211: update aggregation documentation Johannes Berg
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=1276151288.3623.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Sujith.Manoharan@atheros.com \
--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;
as well as URLs for NNTP newsgroup(s).