From: Dave <kilroyd@googlemail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Dave <kilroyd@googlemail.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH] [try 2] orinoco: more reliable scan handling
Date: Tue, 04 Dec 2007 18:59:14 +0000 [thread overview]
Message-ID: <4755A382.5000806@gmail.com> (raw)
In-Reply-To: <1196790911.14982.4.camel@localhost.localdomain>
Dan Williams wrote:
> On Sat, 2007-11-24 at 21:48 +0000, Dave wrote:
>> Dan Williams wrote:
>>> Bring scan result handling more in line with drivers like ipw. Scan
>>> results are aggregated and a BSS dropped after 15 seconds if no beacon
>>> is received. This allows the driver to interact better with userspace
>>> where more than one process may request scans or results at any time.
>> I've only seen this recently, and am using it as a basis for some other changes. However I've noticed a couple issues:
>>
>>> +static int orinoco_process_scan_results(struct net_device *dev,
>>> + unsigned char *buf,
>>> + int len)
>>> +{
>> <snip>
>>> + /* Try to update an existing bss first */
>>> + list_for_each_entry(bss, &priv->bss_list, list) {
>>> + if (compare_ether_addr(bss->bss.a.bssid, atom->a.bssid))
>> if (!compare_ether_addr(bss->bss.a.bssid, atom->a.bssid))
>>
>> So that we proceed to the next bss when ether_addr doesn't match. Otherwise this loop never matches.
>
> compare_ether_addr(), like memcmp, returns 0 when the two arguments
> match. So I think this is OK.
Agreed. My mistake.
> What the loop should be doing is trying
> to find a BSSID + ESSID match and just update the last_seen value, which
> from my reread is what it's doing here...
Agreed.
If something in userspace triggers a scan every 10 seconds, the scan results will always be the same (the oldest).
If that is the desired behaviour (or we don't care about this misuse) this is fine. Personally I'd expect the results to be updated, but I've only recently started messing with wireless drivers.
Thanks,
Dave.
next prev parent reply other threads:[~2007-12-04 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 16:17 [RFC PATCH] orinoco: more reliable scan handling Dan Williams
2007-10-10 18:32 ` John W. Linville
2007-10-11 3:56 ` [RFC PATCH] [try 2] " Dan Williams
[not found] ` <47489C2D.7030606@gmail.com>
2007-12-04 17:42 ` Dan Williams
2007-12-04 18:19 ` John W. Linville
2007-12-04 17:55 ` Dan Williams
2007-12-04 18:59 ` Dave [this message]
2007-12-04 20:19 ` 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=4755A382.5000806@gmail.com \
--to=kilroyd@googlemail.com \
--cc=dcbw@redhat.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 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.