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: Mon, 14 Nov 2011 16:37:21 +0100	[thread overview]
Message-ID: <1321285041.10264.14.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1320844134.3845.61.camel@jlt3.sipsolutions.net> (sfid-20111109_140902_212963_943EDBDE)

Another thought that crossed my mind is how to handle off-channel TDLS.
I'm sure it'll become a requirement fairly soon, and I think we'll want
to design it into the stack.

I wish I could gather a few people into a room and sit there for a few
days brainstorming how it should look like (and how to implement
backward compatibility!) .... :-)

Anyway so my thought about off-channel TDLS was -- should we maybe
assign a channel to each station? Obviously each station associated to
an AP would have the same channel. That might make channel switching
(CSA) a little interesting, but hey ...

In our device we'll probably not handle it this way, but it seems like
the best abstraction?

Also I think we should probably have some explicit channel handling. I'm
not thinking about scanning/off-channel operations but about actual use
of the channel. There could be some weight requests for the different
channels depending on airtime needs, but ultimately the driver will
probably have to make the timing decisions and will communicate that up
to make negotiation between devices possible for this. NoA might be
handled in the driver right now, but I think TDLS negotiation for
channels would not be, and there you need timings...

johannes



  parent reply	other threads:[~2011-11-14 15:37 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
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 [this message]
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=1321285041.10264.14.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).