linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: off- & multi-channel operation
Date: Fri, 11 Nov 2011 13:48:15 +0100	[thread overview]
Message-ID: <1321015695.3977.167.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1320844134.3845.61.camel@jlt3.sipsolutions.net> (sfid-20111109_140902_212963_943EDBDE)

On Wed, 2011-11-09 at 14:08 +0100, Johannes Berg wrote:

> How do we want to handle these things? I'm sure I want the drivers to
> handle multi-channel operation fairly transparently, with multiple
> (hardware) queues (in the driver), so mac80211 doesn't have to
> start/stop the queues continuously and can just transmit on that
> interface, the frame might only go out a bit later.

Hmm, off-channel TDLS is also an interesting case ...

Maybe we need to have a channel for each station? And get timing info
from the device somehow for all the negotiation? Obviously stations
connected to an AP would all have the same channel etc...

johannes


  parent reply	other threads:[~2011-11-11 12:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 13:08 off- & multi-channel operation Johannes Berg
2011-11-09 17:48 ` Ben Greear
2011-11-09 18:15   ` Johannes Berg
2011-11-09 19:54     ` Ben Greear
2011-11-11 10:13       ` Johannes Berg
2011-11-11 17:54         ` Ben Greear
2011-11-11 18:00           ` Johannes Berg
2011-11-11 12:48 ` Johannes Berg [this message]
2011-11-11 13:16 ` Stanislaw Gruszka
2011-11-11 13:26   ` Johannes Berg
2011-11-12 22:46 ` Adrian Chadd
2011-11-14  7:52   ` Johannes Berg
2011-11-14 15:25 ` Johannes Berg
2011-11-14 15:37 ` Johannes Berg
2011-11-27  6:07   ` Adrian Chadd

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=1321015695.3977.167.camel@jlt3.sipsolutions.net \
    --to=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).