linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	Arend van Spriel <arend@broadcom.com>,
	Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [PATCH 0/7] Improvements to software scanning
Date: Wed, 30 Jan 2013 14:34:19 -0500	[thread overview]
Message-ID: <20130130193419.GG2167@tuxdriver.com> (raw)
In-Reply-To: <1359503255-18270-1-git-send-email-seth.forshee@canonical.com>

On Tue, Jan 29, 2013 at 05:47:28PM -0600, Seth Forshee wrote:
> This patch series fixes a number of problems observed during software
> scanning, as described in [1].
> 
> The first four patches implement improved queue handling during
> off-channel operation and add some needed flushing of the hardware
> queues, as suggested by Johannes in [2]. This includes adding a new
> queue stop reason of off-channel operation, a transmit path for frames
> which do need to be transmitted when off-channel, and some improvements
> in error handling.
> 
> The last three fix a problem specific to brcmsmac (and likely b43,
> though I don't have hardware for testing b43). Broadcom hardware
> actively clears the PM bit in frame control whenever the hardware is not
> configured correctly, and since wireless drivers have no knowledge of
> off-channel powersave such configuration cannot be done. The patches
> expand the driver powersave configuration with an off-channel state and
> update brcmsmac to make use of it.
> 
> Johannes: I have a couple of comments/questions for you related to these
> patches.
> 
> First, in the patches I've added an offchan_tx_ok argument to the tx
> operations, but this seems a little awkward to me since it has to be
> propogated down through a fairly deep call stack. The alternative idea
> that occurred to me is to use a tx control flag, but that seems to be
> pretty crowded. Any thoughts?
> 
> Second, I attempted to test these patches with iwlwifi (Centrino
> Advanced-N 6235) to verify that I didn't break anything for drivers with
> hw scanning. My standard test for this involves running iperf while
> triggering nearly continuous scans, but I'm seeing lots of problems
> running a tcp iperf test even with unpatched 3.8-rc4. iperf with udp
> does fine in either direction. I haven't had time to do any kind of
> debugging yet, but I thought you'd want to know.
> 
> Thanks,
> Seth
> 
> [1] http://marc.info/?l=linux-wireless&m=135766865110986&w=2
> [2] http://marc.info/?l=linux-wireless&m=135838252227053&w=2
> 
> 
> Seth Forshee (7):
>   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
>   mac80211: Expand powersave configuration flag to be two bits
>   mac80211: Add off-channel powersave state
>   brcmsmac: Add support for off-channel powersave

Johannes,

Please take the brcsmac patch through your tree if/when you take
the others.

Thanks!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2013-01-30 19:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 23:47 [PATCH 0/7] Improvements to software scanning Seth Forshee
2013-01-29 23:47 ` [PATCH 1/7] mac80211: Return a status for tx operations Seth Forshee
2013-01-29 23:47 ` [PATCH 2/7] mac80211: Fix tx queue handling during scans Seth Forshee
2013-01-31 15:14   ` Johannes Berg
2013-01-31 16:14     ` Seth Forshee
2013-01-29 23:47 ` [PATCH 3/7] mac80211: Improve error handling for off-channel operation Seth Forshee
2013-01-31 15:15   ` Johannes Berg
2013-01-31 16:17     ` Seth Forshee
2013-01-29 23:47 ` [PATCH 4/7] mac80211: Add flushes before going off-channel Seth Forshee
2013-01-29 23:47 ` [PATCH 5/7] mac80211: Expand powersave configuration flag to be two bits Seth Forshee
2013-01-31 15:20   ` Johannes Berg
2013-01-31 16:33     ` Seth Forshee
2013-01-31 16:53       ` Johannes Berg
2013-01-31 17:18         ` Seth Forshee
2013-01-31 17:50           ` Johannes Berg
2013-02-05 22:51             ` Seth Forshee
2013-02-06 16:48               ` Johannes Berg
2013-02-06 17:09                 ` Seth Forshee
2013-02-06 17:44                   ` Johannes Berg
2013-02-06 18:02                     ` Seth Forshee
2013-02-06 21:30                       ` Johannes Berg
2013-01-29 23:47 ` [PATCH 6/7] mac80211: Add off-channel powersave state Seth Forshee
2013-01-29 23:47 ` [PATCH 7/7] brcmsmac: Add support for off-channel powersave Seth Forshee
2013-01-29 23:56   ` Julian Calaby
2013-01-30  5:28     ` Seth Forshee
2013-01-30 19:34 ` John W. Linville [this message]
2013-01-30 21:27 ` [PATCH 0/7] Improvements to software scanning Arend van Spriel
2013-01-30 21:53   ` Seth Forshee
2013-01-31 15:04 ` Johannes Berg
2013-01-31 15:08   ` Johannes Berg
2013-01-31 16:02     ` Seth Forshee
2013-01-31 15:48   ` 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=20130130193419.GG2167@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    --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).