From: Seth Forshee <seth.forshee@canonical.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
Seth Forshee <seth.forshee@canonical.com>
Subject: [PATCH 0/4] Improve queue handling for off-channel operation
Date: Wed, 6 Feb 2013 09:01:09 -0600 [thread overview]
Message-ID: <1360162873-17240-1-git-send-email-seth.forshee@canonical.com> (raw)
Hi Johannes,
Here are some updates to the tx queue handling patches during
off-channel operation that were part of the larger series I sent last
week. I didn't see any reason to sit on these while I finished
implementing the powersave changes. This includes the patches to return
a status from tx operations, add an off-channel queue stop reason, and
improve error handling when going off-channel.
Changes since v1:
* Add unlikely() to the off-channel condition in ieee80211_tx_frags()
* Expand the queue stop reasons that will cause off-channel frames to
be dropped to include everything except the off-channel stop reason
* Remove changes to abort scans when sending of probe request frames
failed
Thanks,
Seth
Seth Forshee (4):
mac80211: Return a status for tx operations
mac80211: Fix tx queue handling during scans
mac80211: Improve error handling for off-channel operation
mac80211: Add flushes before going off-channel
net/mac80211/agg-tx.c | 4 +-
net/mac80211/cfg.c | 2 +-
net/mac80211/ht.c | 2 +-
net/mac80211/ieee80211_i.h | 70 ++++++++++++++++++------
net/mac80211/mlme.c | 6 +-
net/mac80211/offchannel.c | 55 +++++++++++--------
net/mac80211/scan.c | 16 +++++-
net/mac80211/sta_info.c | 2 +-
net/mac80211/tx.c | 130 +++++++++++++++++++++++++-------------------
net/mac80211/util.c | 3 +-
10 files changed, 182 insertions(+), 108 deletions(-)
next reply other threads:[~2013-02-06 15:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 15:01 Seth Forshee [this message]
2013-02-06 15:01 ` [PATCH 1/4] mac80211: Return a status for tx operations Seth Forshee
2013-02-06 15:01 ` [PATCH 2/4] mac80211: Fix tx queue handling during scans Seth Forshee
2013-02-06 15:01 ` [PATCH 3/4] mac80211: Improve error handling for off-channel operation Seth Forshee
2013-02-06 21:44 ` Johannes Berg
2013-02-06 22:05 ` Seth Forshee
2013-02-06 22:10 ` Johannes Berg
2013-02-06 22:20 ` Seth Forshee
2013-02-06 22:26 ` Johannes Berg
2013-02-06 22:30 ` Johannes Berg
2013-02-07 17:54 ` [PATCH v3 1/2] mac80211: Fix tx queue handling during scans Seth Forshee
2013-02-07 17:54 ` [PATCH v3 2/2] mac80211: Add flushes before going off-channel Seth Forshee
2013-02-08 9:03 ` [PATCH v3 1/2] mac80211: Fix tx queue handling during scans Johannes Berg
2013-02-08 17:11 ` Seth Forshee
2013-02-08 17:17 ` Johannes Berg
2013-02-08 18:10 ` Seth Forshee
2013-02-08 19:05 ` Johannes Berg
2013-02-08 20:46 ` Seth Forshee
2013-02-08 20:53 ` Johannes Berg
2013-02-11 17:18 ` Seth Forshee
2013-02-11 17:21 ` [PATCH v4 " Seth Forshee
2013-02-11 17:21 ` [PATCH v4 2/2] mac80211: Add flushes before going off-channel Seth Forshee
2013-02-11 21:40 ` [PATCH v4 1/2] mac80211: Fix tx queue handling during scans Johannes Berg
2013-02-11 21:50 ` Seth Forshee
2013-02-06 15:01 ` [PATCH 4/4] mac80211: Add flushes before going off-channel Seth Forshee
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=1360162873-17240-1-git-send-email-seth.forshee@canonical.com \
--to=seth.forshee@canonical.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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).