From: Samuel Ortiz <sameo@linux.intel.com>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] libertas: cfg80211 support
Date: Thu, 11 Feb 2010 13:01:34 +0100 [thread overview]
Message-ID: <20100211120133.GA3136@sortiz.org> (raw)
In-Reply-To: <201002041052.00858.holgerschurig@gmail.com>
Hi Holger,
On Thu, Feb 04, 2010 at 10:52:00AM +0100, Holger Schurig wrote:
> > + Slightly changed the scanning state machine: The scan
> > worker is scheduled from the scan response handler, and
> > we're checking for scan_channel to know if a scan is
> > currently running.
>
> Can you tell my why you change the scanning state machine? What
> was broken with it, or why is it now better?
Well, I wasnt happy with the delayed scan work your patch was using.
First you were delaying the initial work and I dont think it's useful.
Then we were scheduling a new scan work from the scan worker itself. Although
it was also delayed by 300 ms, you still dont have any guarantees that the
previous scan is done when the next scan worker starts.
What I changed is triggerring the scan work whenever the last one is done,
i.e. triggering it from lbs_ret_scan(). This way we have a fully synchronized
scanning state machine.
>
> Also, previously priv->scan_req was the marker that a scan was
> going on. What did it "buy" to you to change this to
> priv->scan_channel?
I guess I could still use scan_req for that purpose.
My initial thought was that you could have 2 lbs_cfg_scan() running at the
same time since you could potentially have a 2nd lbs_cfg_scan() call before
scan_request is actually set. However I believe cfg80211 and nl80211 prevent
that from happening anyway as they call the scan ops under the rtnl lock.
So, as I said, I could probably keep using scan_request.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-02-11 12:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 0:09 [PATCH] libertas: cfg80211 support Samuel Ortiz
2010-02-02 20:36 ` John W. Linville
2010-02-03 9:31 ` Holger Schurig
2010-02-03 12:04 ` Samuel Ortiz
2010-02-03 15:32 ` Holger Schurig
2010-02-03 20:30 ` Dan Williams
2010-02-04 7:28 ` Holger Schurig
2010-02-04 21:49 ` Dan Williams
2010-02-04 9:52 ` Holger Schurig
2010-02-11 12:01 ` Samuel Ortiz [this message]
2010-02-11 12:24 ` Holger Schurig
2010-02-04 10:11 ` Holger Schurig
2010-02-11 12:03 ` Samuel Ortiz
2010-02-04 13:44 ` [PATCH] libertas+cfg80211: better disconnect support Holger Schurig
2010-02-15 10:46 ` [PATCH] libertas: cfg80211 support Holger Schurig
[not found] ` <cdd918981002240005o1fa50956yfb2a692716c06a55@mail.gmail.com>
2010-02-24 23:35 ` Dan Williams
2010-02-25 8:42 ` David MOUSSAUD
2010-02-25 8:48 ` Johannes Berg
2010-02-25 18:05 ` Andrey Yurovsky
2010-03-07 17:32 ` Kalle Valo
2010-03-07 17:52 ` Gábor Stefanik
2010-02-24 8:22 ` David MOUSSAUD
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=20100211120133.GA3136@sortiz.org \
--to=sameo@linux.intel.com \
--cc=holgerschurig@gmail.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;
as well as URLs for NNTP newsgroup(s).