linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Bing Zhao" <bzhao@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	"Sam Leffler" <sleffler@chromium.org>,
	"Amitkumar Karwar" <akarwar@marvell.com>
Subject: Re: [PATCH v6 3/6] cfg80211: add scan flag to indicate its priority
Date: Fri, 19 Oct 2012 10:00:43 +0200	[thread overview]
Message-ID: <508108AB.2010801@broadcom.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F7043083B80E682@SC-VEXCH1.marvell.com>

On 10/18/2012 08:44 PM, Bing Zhao wrote:
> Hi Arend,
>
>>> From: Sam Leffler <sleffler@chromium.org>
>>>
>>> Add NL80211_SCAN_FLAG_LOW_PRIORITY flag support. It tells drivers
>>> that this is a low priority scan request, so that they can take
>>> necessary action.
>>> Drivers need to advertise low priority scan capability during
>>> registration.
>>
>> I missed the previous versions of this patch series, but what 'necessary
>> action' is needed for a low priority scan request. Patch #6 gives a clue
>> so my assumption is that a low prio scan will be *aborted* when
>> associated and data traffic is available. Is that correct? Could it also
>
> It's up to the driver to decide and implement the 'low priority scan' feature.
> The driver can defer or abort the low priority scan request depending on various conditions.
> For example, when heavy data traffic is on going you may want to abort the scan.

Thanks, Bing

I always find such answer tricky. Seeing where this is coming from I 
suspect there is some high-level expectation from user-space 
perspective. I suspect it is something like: A low-prio scan should not 
affect a data transfer (iperf, nfs i/o, etc.) noticably.

Thanks for collecting the reading material ;-)

Gr. AvS



  reply	other threads:[~2012-10-19  8:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  6:34 [PATCH v6 0/6] add scan flags support Bing Zhao
2012-10-18  6:34 ` [PATCH v6 1/6] {nl,cfg}80211: add a flags word to scan requests Bing Zhao
2012-10-18  6:34 ` [PATCH v6 2/6] cfg80211: code rearrangement to avoid forward declarations Bing Zhao
2012-10-18  6:34 ` [PATCH v6 3/6] cfg80211: add scan flag to indicate its priority Bing Zhao
2012-10-18  7:26   ` Arend van Spriel
2012-10-18 18:44     ` Bing Zhao
2012-10-19  8:00       ` Arend van Spriel [this message]
2012-10-18  6:34 ` [PATCH v6 4/6] wireless: use OR operation to set wiphy features Bing Zhao
2012-10-24  8:59   ` Kalle Valo
2012-10-24  9:01     ` Johannes Berg
2012-10-24  9:03       ` Kalle Valo
2012-10-24  9:10         ` Johannes Berg
2012-10-18  6:34 ` [PATCH v6 5/6] cfg80211: add support for flushing old scan results Bing Zhao
2012-10-18  6:34 ` [PATCH v6 6/6] mac80211: add support for tx to abort low priority scan requests Bing Zhao

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=508108AB.2010801@broadcom.com \
    --to=arend@broadcom.com \
    --cc=akarwar@marvell.com \
    --cc=bzhao@marvell.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sleffler@chromium.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).