From: Steve Brown <sbrown@cortland.com>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: 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: Fri, 14 Jan 2011 19:55:36 -0500 [thread overview]
Message-ID: <1295052936.2253.5.camel@mythtv.ewol.com> (raw)
In-Reply-To: <AANLkTi=WTUiy1DYNhE12_KZp8QFUrWebY2Cpzud5P0b3@mail.gmail.com>
On Sat, 2011-01-15 at 00:19 +0100, Björn Smedman wrote:
> Thank you for your efforts to get multi-vifs working better.
>
> This is another comment that is a little out of place but when I see
> the identifier beacon_interval in this context I cannot help bringing
> up per-vif settings as a related problem: If I read the code (or
> rather the lack of code) correctly the beacon interval of the last (or
> first?) beaconing vif added will be used to set up beacon tx, whereas
> the actual beacon contents will reflect the beacon intervals
> configured for individual vifs which may all be different... The same
> goes for e.g. tx queue configuration, no?
>
> It feels like we need a general multi-vif cleanup here but it's too
> big for me unfortunately.
>
> /Björn
> _______________________________________________
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.
Steve
next prev parent reply other threads:[~2011-01-15 0:55 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 ` Steve Brown [this message]
2011-01-15 1:20 ` [ath9k-devel] " Björn Smedman
2011-01-15 11:07 ` Jouni Malinen
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=1295052936.2253.5.camel@mythtv.ewol.com \
--to=sbrown@cortland.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=bjorn.smedman@venatech.se \
--cc=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).