From: Felix Fietkau <nbd@openwrt.org>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] ath9k: performance regressions / tx semi-stuck somehow
Date: Thu, 22 Jul 2010 02:32:47 +0200 [thread overview]
Message-ID: <4C4791AF.8040909@openwrt.org> (raw)
In-Reply-To: <AANLkTimQ7O2nOmh2Rda3d_PKWbS2WlGVBHYMCuhxW10W@mail.gmail.com>
On 2010-07-22 12:17 AM, Björn Smedman wrote:
> Hi all,
>
> I just tried out compat-wireless-2010-07-16 on AR913x (with
> openwrt/trunk@r22321) and saw some weird performance problems.
>
> That's in exactly the same spot I was getting 16Mbps consistently with
> AP was 11n!
>
> Any debuging I can do to help? Bisecting is unfortunately a lot of
> work on this embedded system...
Could you please try if the earlier version that was in OpenWrt
(2010-07-06) has the same issues?
- Felix
next prev parent reply other threads:[~2010-07-22 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 22:17 ath9k: performance regressions / tx semi-stuck somehow Björn Smedman
2010-07-22 0:32 ` Felix Fietkau [this message]
2010-07-22 22:56 ` [ath9k-devel] " Björn Smedman
2010-07-26 23:36 ` Björn Smedman
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=4C4791AF.8040909@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=bjorn.smedman@venatech.se \
--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;
as well as URLs for NNTP newsgroup(s).