From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mac80211: fix scan state machine
Date: Wed, 21 Dec 2011 21:07:48 +0530 [thread overview]
Message-ID: <4EF1FD4C.3070507@qca.qualcomm.com> (raw)
In-Reply-To: <CAGXE3d-Ntrz7WUXMKBHP2oyX1YBFvqyDHU96x9xGb__C=O8Mtw@mail.gmail.com>
On Wednesday 21 December 2011 09:01 PM, Helmut Schaa wrote:
> Hi,
Hi Helmut,
>
> On Wed, Dec 21, 2011 at 3:51 PM, Mohammed Shafi Shajakhan
> <mohammed@qca.qualcomm.com> wrote:
>> From: Mohammed Shafi Shajakhan<mohammed@qca.qualcomm.com>
>>
>> when we run high bandwidth UDP traffic and we trigger a scan, the scan
>> state machine seems to be looping in SUSPEND->RESUME->DECISION->SUSPEND
>> and SET_CHANNEL seems to be never called as 'tx_empty' is never true
>> while running UDP traffic. fix this by settting SET_CHANNEL state when
>> we get into RESUME state.
>
> Your analysis looks correct to me. Previously (before the
> simplification patches)
> the logic to always scan at least one channel was put in scan_state_decision but
> maybe it makes sense to have it in scan_state_resume.
thanks for the review.
i compared "ieee80211_scan_state_resume" with the older code's
"ieee80211_scan_state_leave_oper_channel"
>
> So, to me the patch looks good.
>
> Helmut
>
--
thanks,
shafi
prev parent reply other threads:[~2011-12-21 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 14:51 [RFC] mac80211: fix scan state machine Mohammed Shafi Shajakhan
2011-12-21 14:54 ` Mohammed Shafi Shajakhan
2011-12-21 15:31 ` Helmut Schaa
2011-12-21 15:37 ` Mohammed Shafi Shajakhan [this message]
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=4EF1FD4C.3070507@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=helmut.schaa@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.