From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Dan Williams <dcbw@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Aeolus.Yang@atheros.com,
Senthil Balasubramanian <senthilkumar@atheros.com>,
Gaurav.Jauhar@atheros.com, David Miller <davem@davemloft.net>,
Jouni Malinen <j@w1.fi>
Subject: Re: Scan while TX/RX'ing a lot of data
Date: Mon, 18 May 2009 08:38:59 -0400 [thread overview]
Message-ID: <20090518123858.GA2814@tuxdriver.com> (raw)
In-Reply-To: <1242478657.10005.72.camel@johannes.local>
On Sat, May 16, 2009 at 02:57:37PM +0200, Johannes Berg wrote:
> Anyway, bottom line is that I don't think we should change the APIs in
> any way, we should instead make the scan smarter by spreading it out if
> we're active. This even applies to scanning while in an IBSS -- stop
> beaconing, then go scan etc.
ACK
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-05-18 12:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 17:52 Scan while TX/RX'ing a lot of data Luis R. Rodriguez
2009-05-14 18:54 ` Dan Williams
2009-05-14 19:06 ` Johannes Berg
2009-05-14 20:50 ` Dan Williams
2009-05-14 20:53 ` Johannes Berg
2009-05-14 19:07 ` Luis R. Rodriguez
2009-05-14 20:57 ` Dan Williams
2009-05-14 21:26 ` Luis R. Rodriguez
2009-05-14 22:17 ` Luis R. Rodriguez
2009-05-16 6:12 ` Luis R. Rodriguez
2009-05-16 6:15 ` Luis R. Rodriguez
2009-05-16 12:57 ` Johannes Berg
2009-05-18 12:38 ` John W. Linville [this message]
2009-05-18 17:52 ` Luis R. Rodriguez
2009-05-18 13:43 ` Helmut Schaa
2009-05-19 9:06 ` Johannes Berg
2009-05-20 11:41 ` Helmut Schaa
2009-05-20 11:44 ` Johannes Berg
2009-05-20 13:43 ` Helmut Schaa
2009-05-20 13:53 ` Johannes Berg
2009-05-18 18:06 ` Luis R. Rodriguez
2009-05-19 9:09 ` Johannes Berg
2009-05-15 8:11 ` Holger Schurig
2009-05-15 8:31 ` Johannes Berg
2009-05-15 23:15 ` Dan Williams
2009-05-16 12:48 ` Johannes Berg
2009-05-18 15:35 ` 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=20090518123858.GA2814@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Aeolus.Yang@atheros.com \
--cc=Gaurav.Jauhar@atheros.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=senthilkumar@atheros.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.