From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Moving scan logic into work-queue?
Date: Tue, 29 Nov 2011 10:13:49 -0800 [thread overview]
Message-ID: <4ED520DD.8050606@candelatech.com> (raw)
We've talked before about moving the scan logic into the work-queue.
Since my previous attempts at optimizing this code for scanning & off-channel
work didn't stick, I thought I might attempt to convert the scan logic
to the work-queue, with hopes of then being able to make another attempt
at optimizing things for multiple interfaces & potentially off-channel work
items.
Before I start though, I'm hoping for some guidance on how you'd
want this implemented. Or, if you think there are other changes
that should go in first, I'll wait...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2011-11-29 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 18:13 Ben Greear [this message]
2011-11-29 18:15 ` Moving scan logic into work-queue? Johannes Berg
2011-11-29 18:18 ` Ben Greear
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=4ED520DD.8050606@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).