From: Jouni Malinen <j@w1.fi>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: sbrown@cortland.com, greearb@candelatech.com,
ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] [RFC 1/2] ath9k: Fix up hardware mode and beacons with multiple vifs.
Date: Sat, 15 Jan 2011 13:07:51 +0200 [thread overview]
Message-ID: <20110115110751.GA7035@jm.kir.nu> (raw)
In-Reply-To: <AANLkTi=_qAB6aVEbsTBUfpVwTg4GbLsAYbyP0PA2n+NO@mail.gmail.com>
On Sat, Jan 15, 2011 at 02:20:00AM +0100, Björn Smedman wrote:
> 2011/1/15 Steve Brown <sbrown@cortland.com>:
> > For instance, an ap vif has a ~100ms interval and a mesh vif has a
> > ~1000ms interval. I don't see how to avoid a per vif interval.
>
> I agree. We should fix ath9k so it works correctly even if beacon
> interval is different for different vifs (within some reasonable
> limits).
Yes, up to a limit. Handling something like 100 TU on one vif and 1000
TU on another is fine, but something like 100 TU and 103 TU would need
to be forced to use the same interval. I've been thinking of adding some
kind of mechanism for the driver to override Beacon interval in such
cases (which would need to go back all the way to user space to hostapd
in case of AP mode).
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2011-01-15 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 17:27 [RFC 1/2] ath9k: Fix up hardware mode and beacons with multiple vifs greearb
2011-01-14 17:27 ` [RFC 2/2] ath9k: Add 'misc' file to debugfs, fix queue indexes greearb
2011-01-14 18:05 ` [ath9k-devel] [RFC 1/2] ath9k: Fix up hardware mode and beacons with multiple vifs Felix Fietkau
2011-01-14 18:16 ` Ben Greear
2011-01-15 1:41 ` Björn Smedman
2011-01-15 14:54 ` Ben Greear
2011-01-14 18:58 ` Steve Brown
2011-01-14 19:12 ` Ben Greear
2011-01-14 23:19 ` Björn Smedman
2011-01-14 23:24 ` Ben Greear
2011-01-15 0:55 ` [ath9k-devel] " Steve Brown
2011-01-15 1:20 ` Björn Smedman
2011-01-15 11:07 ` Jouni Malinen [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=20110115110751.GA7035@jm.kir.nu \
--to=j@w1.fi \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=bjorn.smedman@venatech.se \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sbrown@cortland.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).