From: Johannes Berg <johannes@sipsolutions.net>
To: Tim Harvey <harvey.tim@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC] mac80211 default tx_last_beacon false (congestion)
Date: Thu, 09 Dec 2010 22:21:34 +0100 [thread overview]
Message-ID: <1291929694.3540.39.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1291929345-8066-1-git-send-email-harvey.tim@gmail.com>
On Thu, 2010-12-09 at 13:15 -0800, Tim Harvey wrote:
> The 802.11 spec states that the STA that generated the last Beacon frame shall
> be the STA that response to a probe request. This is important for congestion
> reduction when a probe request is received - only 1 node in an adhoc BSS
> will transmit a response. While mac80211 drivers should provide the
> tx_last_beacon function to report if they transmitted the last beacon many
> do not. As an attempt to reduce probe response congestion default this
> to 0 such that a node not implementing this capability does not contribute
> to unnecessary congestion.
>
> In a modern medium sized office environment I see upwards of 100 probe
> requests per second received at a given node from various hardware/OS/drivers
> doing zeroconf 'active probing' as opposed to passively listening for beacons.
> With a modest 10-node adhoc network consisting of drivers that do not implement
> this tx_last_beacon feature, I have seen this result in the simultaneous xmit
> of probe responses accumulating to 500 probe responses per second because of
> collisions which brings the adhoc network to its knees as well as causes
> needless congestion.
FWIW, I'm OK with this. It shouldn't really have much adverse effect.
johannes
prev parent reply other threads:[~2010-12-09 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 21:15 [PATCH RFC] mac80211 default tx_last_beacon false (congestion) Tim Harvey
2010-12-09 21:21 ` Johannes Berg [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=1291929694.3540.39.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=harvey.tim@gmail.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