From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Michal Kazior <michal.kazior@tieto.com>
Subject: [RFC 0/2] mac80211 queue redesign
Date: Wed, 28 Mar 2012 11:13:46 +0200 [thread overview]
Message-ID: <20120328091346.442543219@sipsolutions.net> (raw)
Here's the queue redesign we've been talking about.
The monitor patch is needed because when a driver actually
uses the new queue feature there isn't any queue to TX
frames on for purely virtual interfaces. This only affects
monitor (AP_VLAN are tied to AP) and only when injecting
frames that don't have a TA matching another interface (as
we bind the frames to that interface then). That, however
is probably the biggest use case (now that monitor-for-AP
is dying). As a consequence, drivers wanting to support
"pure" injection and using the new queue features need to
support the pure monitor interface feature as well. Also,
the pure monitor feature will help implement monitor mode
on devices where that is mutually exclusive with other
modes (like iwlwifi.)
The monitor feature I've tested in hwsim, it works. The
queue feature isn't tested at all, I haven't even done
any kind of regression tests for drivers not using it.
Thanks goes out to everybody I discussed this with (on
IRC or elsewhere), and also Michal for reviewing a first
version of this patch :-)
johannes
next reply other threads:[~2012-03-28 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:13 Johannes Berg [this message]
2012-03-28 9:13 ` [RFC 1/2] mac80211: add explicit monitor interface if needed Johannes Berg
2012-03-29 20:09 ` Eliad Peller
2012-03-30 6:39 ` Johannes Berg
2012-03-28 9:13 ` [RFC 2/2] mac80211: add improved HW queue control Johannes Berg
2012-03-28 9:26 ` Johannes Berg
2012-04-02 9:22 ` [RFC v2] " Johannes Berg
2012-03-28 12:00 ` [RFC 0/2] mac80211 queue redesign Johannes Berg
2012-03-28 12:49 ` 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=20120328091346.442543219@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).