From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath9k: improve max rate retry handling
Date: Wed, 27 Jan 2010 14:43:51 -0500 [thread overview]
Message-ID: <20100127194351.GI2962@tuxdriver.com> (raw)
In-Reply-To: <43e72e891001270938q4bba2a08wa02c8db858ee5954@mail.gmail.com>
On Wed, Jan 27, 2010 at 09:38:06AM -0800, Luis R. Rodriguez wrote:
> On Sat, Jan 23, 2010 at 6:26 PM, Felix Fietkau <nbd@openwrt.org> wrote:
> > ath9k currently forces hw->max_rate_tries to 4 to work around rate
> > control inefficiencies. This has some negative side effects, such as
> > rate_control_send_low also using a maximum of 4 tries, which could
> > negatively affect reliability of unicast management frames.
> > This patch pushes the retry limit to the rate control instead, and
> > allows it to use more tries on the last stage to prevent unnecessary
> > packet loss.
>
> If this is not merged yet and if its not too much trouble, would you
> mind splitting this into two separate patches, one which increases the
> MRR segment retry count, and the other which does what the current
> commit log says? Reason is increasing the MRR segment retry count
> might be useful as a cherry pick for older kernels.
It's already merged...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-01-27 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 2:26 [PATCH] ath9k: improve max rate retry handling Felix Fietkau
2010-01-27 17:38 ` Luis R. Rodriguez
2010-01-27 19:43 ` John W. Linville [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=20100127194351.GI2962@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--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 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.