All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <Kalle.Valo@nokia.com>
To: Jouni Malinen <j@w1.fi>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Michael Buesch <mb@bu3sch.de>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Ben Greear <greearb@candelatech.com>,
	Michael Wu <flamingice@sourmilk.net>, Jiri Benc <jbenc@suse.cz>
Subject: Re: [RFC] b43: multiple MAC addresses support
Date: Mon, 12 Nov 2007 13:14:11 +0200	[thread overview]
Message-ID: <87pryfd8cc.fsf@nokia.com> (raw)
In-Reply-To: <20071111025808.GK4031@jm.kir.nu> (ext Jouni Malinen's message of "Sat\, 10 Nov 2007 18\:58\:08 -0800")

Jouni Malinen <j@w1.fi> writes:

> On Fri, Nov 09, 2007 at 11:52:30AM +0100, Johannes Berg wrote:
>
>> Something I'm not clear on right now is the timing of it all. If there
>> are say two BSSes, the driver can simply program the hardware to half
>> the beacon period and then the beacons will alternate. But if there are
>> seven BSSes, the beacon period might not be divisible by seven so timing
>> errors will happen and, worse yet, accumulate. Does hostapd somehow
>> account for this? Or should the beaconing work completely differently,
>> for example with all N beacons sent in a burst?
>
> You could always modify the beacon period to a suitable number that
> would be divisible by whatever number of BSSes there are and/or add
> empty slot to move from, say, 7 to 8, and just not send a beacon at some
> of the slots. Sending a burst of all beacons at the same time is also a
> valid option up to a certain limit on how long a time would be allocated
> for this. However, this may have some timing issues when there are
> multiple power save buffered broadcast/multicast frames waiting to be
> sent out. In general, it would be good to try to send the beacon frames
> as close to their correct time as possible to allow power saving
> stations to remain asleep most of the time.

Exactly, it is important for small mobile devices that beacons are
sent at the correct time. For example, I have seen broken APs which
Target Beacon Transmission Time fluctuates and Nokia N800 has high
power consumption because of that.

-- 
Kalle Valo

  reply	other threads:[~2007-11-12 11:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09  1:43 [RFC] b43: multiple MAC addresses support Johannes Berg
2007-11-09 10:33 ` Johannes Berg
2007-11-09 10:52 ` Johannes Berg
2007-11-11  2:58   ` Jouni Malinen
2007-11-12 11:14     ` Kalle Valo [this message]
2007-11-13 11:26       ` Johannes Berg
2007-11-15  9:35         ` Kalle Valo
2007-11-15 16:40           ` Johannes Berg
2007-11-18 23:02         ` Jouni Malinen
2007-11-19 14:50           ` Johannes Berg
2007-11-13 14:14       ` Johannes Berg
2007-11-12 12:02     ` Johannes Berg
2007-11-18 23:47       ` Jouni Malinen
2007-11-19 14:49         ` Johannes Berg
2007-11-09 10:53 ` [RFC] b43: fix multi MAC address hardware crypto support Johannes Berg
2007-11-09 12:39   ` Johannes Berg
2007-11-10  1:21   ` [RFC v2] " Johannes Berg
2007-11-09 12:25 ` [RFC] b43: multiple MAC addresses support Johannes Berg
2007-11-10  1:20 ` [RFC v2] " Johannes Berg
2007-11-10  1:53 ` [RFC] " Johannes Berg
2007-11-10 21:34   ` Johannes Berg

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=87pryfd8cc.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=flamingice@sourmilk.net \
    --cc=greearb@candelatech.com \
    --cc=j@w1.fi \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.