From: Felix Fietkau <nbd@openwrt.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] minstrel: improve performance for non-MRR drivers
Date: Wed, 15 Oct 2008 22:02:51 +0200 [thread overview]
Message-ID: <48F64C6B.5010801@openwrt.org> (raw)
In-Reply-To: <20081015194803.GB27688@tuxdriver.com>
John W. Linville wrote:
> On Wed, Oct 15, 2008 at 07:13:59PM +0200, Felix Fietkau wrote:
>> This patch enhances minstrel's performance for non-MRR setups,
>> by preventing it from sampling slower rates with >95% success
>> probability and by putting at least 1 non-sample frame between
>> several sample frames.
>>
>> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>> ---
>> This patch depends on the rate control API rewrite patch.
>
> Hah! Which one...? :-)
Should work with Johannes' v3, if it doesn't, please let me know ;)
- Felix
prev parent reply other threads:[~2008-10-15 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 17:13 [PATCH] minstrel: improve performance for non-MRR drivers Felix Fietkau
2008-10-15 19:48 ` John W. Linville
2008-10-15 20:02 ` Felix Fietkau [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=48F64C6B.5010801@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).