From: Zhu Yi <yi.zhu@intel.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 3/3] mac80211: debugfs support for TSM and DLS
Date: Thu, 24 May 2007 15:51:24 +0800 [thread overview]
Message-ID: <1179993084.6150.43.camel@debian.sh.intel.com> (raw)
In-Reply-To: <200705240012.51922.flamingice@sourmilk.net>
On Thu, 2007-05-24 at 00:12 -0700, Michael Wu wrote:
> These chunks were present in the second patch of this series.
Yup. Will remove.
> So, who is going to be responsible for configuring DLS and TS? If we're going
> to leave this policy up to userspace.. why not implement most of the DLS
> handshake/teardown code in wpa_supplicant directly? It would make the
> remaining DLS code in the kernel much more straightforward.
Agreed. The end users should never use the debugfs stuff. These symbols
are exported for debug and testing. I'd agree to move the policy things
to wpa_supplicant.
> However, that's still more of an implementation detail. I'm curious about how
> DLS would actually get initiated and used if I am, for example, transferring
> a large file from one STA to another on the same AP. It seems like the sort
> of information needed to make this decision are similar to what is needed to
> decide when to set up BA.
In the DLS request side, with this patch, you can setup the target MAC
address via debugfs "dls_mac" and set 1 to "dls_op" (of course, these
will be done by wpa_supplicant in the future). So that mac80211 will
initiate DLS setup process. In the receiver side, currently, it accepts
or denies the DLS request based on the debugfs "dls_op" value. In the
future, the decision should be done by userspace via wpa_supplicant or
cfg80211.
Thanks,
-yi
next prev parent reply other threads:[~2007-05-24 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 5:15 [PATCH 3/3] mac80211: debugfs support for TSM and DLS Zhu Yi
2007-05-24 7:12 ` Michael Wu
2007-05-24 7:51 ` Zhu Yi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 11:52 Zhu Yi
2007-05-25 16:20 ` Randy Dunlap
2007-05-25 16:26 ` Michael Buesch
2007-05-28 1:43 ` Zhu Yi
2007-06-06 8:22 Zhu Yi
2007-06-07 20:39 ` Jiri Benc
2007-06-08 1:17 ` Zhu Yi
2007-06-08 9:59 ` Jiri Benc
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=1179993084.6150.43.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=flamingice@sourmilk.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).