linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [Take 2] mac80211 IEEE802.11e/WMM code cleanup
Date: Tue, 12 Jun 2007 16:06:09 +0800	[thread overview]
Message-ID: <1181635570.4758.22.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1181584907.29767.30.camel@johannes.berg>

On Mon, 2007-06-11 at 20:01 +0200, Johannes Berg wrote:
> Hi Yi,
> 
> In sta_process_dls_req, you currently always accept DLS. I'm not sure
> how well power save mode works in mac80211 (probably not at all, someone
> versed in 802.11 should probably look at it some time soon), but once
> DLS is set up power saving must be disabled by the DLS peer. This,
> however, possibly leads to battery lifetime diminishing, so always
> accepting the direct link might not be desirable. Any thoughts?

You are right. I once had the debugfs file on the DLS request response
side to to indicate accept or deny all DLS requests. But after a second
thought, maybe a MAC list is better? But this is just for testing not a
real API.

> Should we have user-space controlled list of DLS possible DLS peers? Or
> call out to userspace via nl80211 to make a decision? The list would be
> easy by simply adding a sta_info for a possible DLS peer, callout also
> shouldn't be too hard by sending a message to some QoS nl80211 multicast
> group and possibly not responding to the DLS request at all when our
> userspace doesn't accept it (that way it'll just time out on the other
> side).

Right. For the real API, I'd prefer the kernel to send an event to
userspace (daemon) via netlink (nl80211) and let user space to make the
decision. This way mac80211 doesn't need to manage the user prefered DLS
list itself. Another benefit is the DLS connection could be established
interactively. For example when a user is VIing in Xwindows, a pop up
window from NetworkManager asks "MAC address XX:XX:.. wants to setup a
DLS connection with you, do you accept?"

Thanks,
-yi

  parent reply	other threads:[~2007-06-12  8:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11  8:59 [Take 2] mac80211 IEEE802.11e/WMM code cleanup Zhu Yi
2007-06-11 18:01 ` Johannes Berg
2007-06-12  7:37   ` Tomas Winkler
2007-06-12  8:18     ` Zhu Yi
2007-06-12 14:21       ` Tomas Winkler
2007-06-12  8:06   ` Zhu Yi [this message]
2007-06-12  9:35     ` Johannes Berg
2007-06-14  7:36     ` Johannes Berg
2007-06-14 16:35       ` Michael Wu
2007-06-16 12:27         ` Johannes Berg
2007-06-16 18:29           ` Michael Wu
2007-06-16 18:51             ` Johannes Berg
2007-06-16 22:16               ` Michael Wu
2007-06-17 12:03                 ` wireless userspace MLME and generic netlink vs. multicast (was: Re: [Take 2] mac80211 IEEE802.11e/WMM code cleanup) Johannes Berg
2007-06-18  2:08                   ` Zhu Yi
2007-06-18  8:46                     ` Johannes Berg
2007-06-17 15:29               ` [Take 2] mac80211 IEEE802.11e/WMM code cleanup Dan Williams
2007-06-18  8:41                 ` Johannes Berg
2007-06-18 11:09                   ` Johannes Berg

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=1181635570.4758.22.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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).