From: Wim Torfs <wtorfs@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: mac80211 and ath9k channel context
Date: Wed, 14 Oct 2015 11:36:57 +0200 [thread overview]
Message-ID: <561E2239.2090006@gmail.com> (raw)
In-Reply-To: <20151013185055.GD50632@ubuntu-hedt>
Hi,
The channel context is mentioned in lots of mails and pieces of code,
but its significance or goal is never mentioned. Could someone please be
so kind to elaborate on this?
I believe the channel context is used to provide some hardware
abstraction towards the driver and mac, such that virtual interfaces are
able to work "in parallel" (to their knowledge they are the sole users)
on the hardware, even when they use different channels. When a virtual
interface needs to perform some action (transmission,...), the channel
is set to the corresponding channel of the interface. Furthermore is the
activation of virtual interfaces done in a round robin manner, where
each channel in the channel context is activated at a periodic interval.
Is this about correct, or am I gravely mistaken?
Thanks,
Kind regards,
Wim.
prev parent reply other threads:[~2015-10-14 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 18:50 [ANN] wireless-regdb: master-2015-10-13 Seth Forshee
2015-10-14 9:36 ` Wim Torfs [this message]
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=561E2239.2090006@gmail.com \
--to=wtorfs@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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).