Linux wireless drivers development
 help / color / mirror / Atom feed
From: Mark Fitzjohn <m.fitzjohn@samsung.com>
To: linux-wireless@vger.kernel.org
Subject: mac80211: impact of netif_carrier_off during roaming
Date: Wed, 19 Jun 2013 10:28:28 +0100	[thread overview]
Message-ID: <004401ce6ccf$5b69e620$123db260$%fitzjohn@samsung.com> (raw)

Hi

I've noticed that during roaming triggered by detection of a significantly
better AP in wpa_supplicant that mac80211 calls netif_carrier_off and then
netif_carrier_on when associated with the new AP.

Does this have any detrimental impact on applications using the wifi
connection or is the assumption that as long as the roam happens in a
reasonable time then applications should tolerate it?

Just wondering if signalling the netif_carrier_off only when the current AP
is lost and there is no immediate alternative AP for the network available
was considered?

Thanks
Mark



             reply	other threads:[~2013-06-19  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  9:28 Mark Fitzjohn [this message]
2013-06-19 13:06 ` mac80211: impact of netif_carrier_off during roaming Dan Williams

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='004401ce6ccf$5b69e620$123db260$%fitzjohn@samsung.com' \
    --to=m.fitzjohn@samsung.com \
    --cc=linux-wireless@vger.kernel.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