From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: reduce the amount of unnecessary traffic on cooked monitor interfaces
Date: Sat, 14 Nov 2009 10:23:27 +0100 [thread overview]
Message-ID: <1258190607.6167.33.camel@johannes.local> (raw)
In-Reply-To: <4AFE1612.5070805@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Sat, 2009-11-14 at 03:29 +0100, Felix Fietkau wrote:
> In order to handle association and authentication in AP mode,
> hostapd needs access to the tx status info of its own frames
> through a cooked monitor interface. Without this patch the
> cooked monitor interfaces also passed on tx status information
> for packets from other virtual interfaces. This creates a
> significant performance issue on embedded system. Hostapd
> tries to work around this by installing a Linux Socket Filter
> that only captures the frames it's interested in, however
> data duplication and socket filter matching still uses up
> enough CPU cycles to be very noticeable on small systems.
> This patch ensures that tx status information of non-injected
> frames does not make it to cooked monitor interfaces.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> + if ((sdata->u.mntr_flags & MONITOR_FLAG_COOK_FRAMES) &&
> + !(info->flags & IEEE80211_TX_CTL_INJECTED) &&
> + (type == IEEE80211_FTYPE_DATA))
> + continue;
> +
This patch also breaks IEEE 802.11 compliance. :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-11-14 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 2:29 [PATCH] mac80211: reduce the amount of unnecessary traffic on cooked monitor interfaces Felix Fietkau
2009-11-14 9:23 ` Johannes Berg [this message]
2009-11-14 9:36 ` 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=1258190607.6167.33.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.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