From: Richard Zidlicky <rz@linux-m68k.org>
To: rt2x00 Users List <users@host1.serialmonkey.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [rt2x00-users] rt2x00: Hardcode TX ack timeout and consume time
Date: Tue, 8 Sep 2009 14:06:09 +0200 [thread overview]
Message-ID: <20090908120608.GA4296@linux-m68k.org> (raw)
In-Reply-To: <200909061514.23611.IvDoorn@gmail.com>
On Sun, Sep 06, 2009 at 03:14:23PM +0200, Ivo van Doorn wrote:
> rt2x00: Hardcode TX ack timeout and consume time
Hi,
it does significantly improve rt73usb performance and stability of ping times.
I can still get almost the double performance and much better ping times when
setting the rate manually.
> John, this patch has not yet been confirmed by any of the above bugzilla reports,
> but I do think this should be merged as soon as possible to 2.6.31 since this issue
> has been marked as regression for quite some time now. :)
imho it should be merged even if it does not fully fix every imaginable problem.
Actually I would wish critical fixes would be merged much more aggressively,
eg rt73usb was critically broken before Pavel Roskin' recent off-by-1 register
access fix - causing all kinds of weird problems probably including filesystem
damage.
Seems some other fixes are also critical - it would be nice to have all important
fixes in eg in 2.6.30.6 (if it ever comes) as it is not quite trivial to cherrypick
them from the list when the code diverges too much from mainline.
Richard
next prev parent reply other threads:[~2009-09-08 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 13:14 rt2x00: Hardcode TX ack timeout and consume time Ivo van Doorn
2009-09-08 12:06 ` Richard Zidlicky [this message]
2009-09-08 12:53 ` [rt2x00-users] " Richard Zidlicky
2009-09-08 18:36 ` John W. Linville
2009-09-10 22:19 ` Ivo van Doorn
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=20090908120608.GA4296@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@host1.serialmonkey.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).