From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT/FYI] mac80211: revert on-channel work optimisations
Date: Tue, 08 Nov 2011 10:08:59 -0800 [thread overview]
Message-ID: <4EB9703B.6030006@candelatech.com> (raw)
In-Reply-To: <1320775001.24797.26.camel@jlt3.sipsolutions.net>
On 11/08/2011 09:56 AM, Johannes Berg wrote:
> On Tue, 2011-11-08 at 09:25 -0800, Ben Greear wrote:
>
>> That's fine by me, I found the code complex as well. All the tmp
>> and scan and active channel pointers makes for a real mess.
>
> Indeed.
>
>> But if
>> you want multiple vifs to work well, then you really need to be able
>> to continue to function on-channel when some other vif is scanning
>> on that channel. My use of the wifi stack requires this to work,
>> so if it takes any significant time to get the new code in I'm going
>> to have to stick with my complex crap.
>
> And I'm not saying you shouldn't, but I think for upstream right now
> it's not really a good thing. I wish I could say otherwise but given the
> bugs we have here etc. I don't really feel very confident.
Are there any open bugs right now that seem to be because of the
scanning and work optimizations, or are you just paranoid that
there are more that are not found or well understood yet?
If there is something reported, I'll make a try at fixing it.
> Now with multi-channel stuff it's all going to change anyway, each vif
> will have its own channel and the device will have to mostly sort out
> the scheduling by itself, ath9k will have to do some tricks in the
> driver, maybe with some help in mac80211, and off-channel stuff will be
> interesting too ...
Is someone already working on this, or planning to do so soon? At least
to me, the multi-channel stuff appears fundamentally broken since I'm
not aware of any NIC that can listen in two channels at once. Flipping
from channel to channel seems like at best it is going to give bad latency,
and probably lots of packet loss as well. What is the use-case for this
feature, anyway?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-11-08 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 17:10 [RFT/FYI] mac80211: revert on-channel work optimisations Johannes Berg
2011-11-08 17:17 ` Ben Greear
2011-11-08 17:18 ` Johannes Berg
2011-11-08 17:25 ` Ben Greear
2011-11-08 17:56 ` Johannes Berg
2011-11-08 18:08 ` Ben Greear [this message]
2011-11-08 18:38 ` Johannes Berg
2011-11-25 11:27 ` Stanislaw Gruszka
2011-11-25 11:29 ` Johannes Berg
2012-02-17 15:44 ` Johannes Berg
2012-02-17 16:13 ` Ben Greear
2012-02-17 18:19 ` Johannes Berg
2012-02-17 18:38 ` Ben Greear
2012-02-18 17:39 ` Stanislaw Gruszka
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=4EB9703B.6030006@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).