linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: Felix Fietkau <nbd@openwrt.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: minstrel_ht should not override user supplied rts setting
Date: Sun, 29 Jan 2012 04:09:06 +0800	[thread overview]
Message-ID: <201201290409.07368.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CALSq=BYOaFSa4zuK0j8vFavjR38wC86Hqcd-sbYZ3b+CBGReJw@mail.gmail.com>

On Sunday, January 29, 2012 04:03:41 you wrote:
> On Sat, Jan 28, 2012 at 11:58 AM, Marek Lindner <lindner_marek@yahoo.de> 
wrote:
> > On Sunday, January 29, 2012 03:17:32 Daniel Halperin wrote:
> >> Adaptive RTS/CTS is important to control for interference---RTS/CTS is
> >> there so that other Wi-Fi devices know not to interfere with your
> >> flow. It may well be the case that this is not a major problem in
> >> whatever your scenario you're working, Marek, but it makes a big
> >> difference in a many bad corner cases.
> > 
> > I am very well aware of what RTS/CTS is for and I am not against using
> > it. However, having the rate algorithm overriding the user setting for a
> > specific rate is extremely hard to grasp or debug.
> > To give you an understanding where I am coming from: In our networks we
> > experienced extremely variable throughput ranging from 30Mbit/s (single
> > stream) to 0.2 Mbit/s in the next second. As you can imagine we were
> > trying to figure out what was going on. After spending some time and
> > losing hair I noticed that the RTS/CTS implementation of our driver
> > (ath9k) is buggy. Every once in a while the nodes would "battle" each
> > other with RTS/CTS packets. Strange enough for us, sometimes no RTS
> > packets were sent and sometimes they would battle. All attempts to
> > disable RTS/CTS for the mere sake of testing(!) was impossible. First I
> > thought ath9k did not properly implement the "iw rts" setting but that
> > wasn't the case. After losing more hair I realized that minstrel_ht, a
> > rate control algorithm(!), was overriding my rts settings but not
> > always(!). The only way to make RTS shut up was to apply the posted
> > patch.
> 
> Can you explain what the low-level behavior of an RTS/CTS "battle" is?
> 
> Abstractly, the behavior you're describing sounds like a buggy driver
> that doesn't obey overheard RTS or CTS packets.

I certainly can explain it but this is for another thread and unrelated to the 
points raised before.

Regards,
Marek

  reply	other threads:[~2012-01-28 20:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28  7:17 [RFC] minstrel_ht should not override user supplied rts Marek Lindner
2012-01-28  7:17 ` [PATCH] mac80211: minstrel_ht should not override user supplied rts setting Marek Lindner
2012-01-28 13:25   ` Felix Fietkau
2012-01-28 18:43     ` Marek Lindner
2012-01-28 18:51       ` Felix Fietkau
2012-01-28 19:17         ` Daniel Halperin
2012-01-28 19:28           ` Felix Fietkau
2012-01-28 19:58           ` Marek Lindner
2012-01-28 20:03             ` Daniel Halperin
2012-01-28 20:09               ` Marek Lindner [this message]
2012-01-28 20:26                 ` Daniel Halperin
2012-01-28 20:35                   ` Marek Lindner
2012-01-28 22:14                     ` Simon Wunderlich
2012-01-29  2:36                       ` Felix Fietkau
2012-01-28 20:20             ` Felix Fietkau
2012-01-28 20:23               ` Marek Lindner
  -- strict thread matches above, loose matches on Subject: below --
2012-06-11  9:52 iwlwifi updates for 3.6 Johannes Berg
2012-06-11  9:53 ` [PATCH 09/13] iwlwifi: comment that setting driver_data overrides info->control Johannes Berg
2014-09-23 10:10   ` [PATCH] mac80211: minstrel_ht should not override user supplied rts setting Guido Gavilanes
2014-09-23 11:44 Guido Gavilanes

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=201201290409.07368.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=dhalperi@cs.washington.edu \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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).