From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: mac80211 work and channel type
Date: Sun, 06 Feb 2011 10:59:09 -0800 [thread overview]
Message-ID: <4D4EEF7D.9020502@candelatech.com> (raw)
Much of the work items currently do not explicitly set a channel-type,
and so default to NO_HT (which is zero).
This currently means that we have to do a channel (type)
change for each work item if we are running HT20 or HT40
on the operating channel. This happens, for instance, during
authentication for stations.
Based on my limited understanding, it seems that it is perfectly
legal to send NO_HT pkts on any channel-type. It seems that you
can also send HT20 on HT40 channel-types. So, would there be any
problem to optimizing the work logic to not change the channel type
if the work channel type fit within the bounds of the current
channel type?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2011-02-06 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D4EEF7D.9020502@candelatech.com \
--to=greearb@candelatech.com \
--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).