From: Joseph Cheek <joseph@cheek.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] dwa-547 very slow
Date: Wed, 21 Jan 2009 00:14:39 -0500 [thread overview]
Message-ID: <4976AF3F.1010705@cheek.com> (raw)
In-Reply-To: <49762E12.8090800@cheek.com>
unforch putting my DIR-655 in 20-only mode made no change in
throughput. I was hoping you had solved one of my throughput issues,
Xaero! No luck tho. Good idea, though!
Joseph
Joseph Cheek wrote:
> hmm, your benchmarks for 20/40 mode in linux are similar to mine in
> throughput. i'll put my router in 20-only mode this eve when i get home
> and see if i can get better transfer rates.
>
> Now if I could just get my cards to maintain IP connectivity when large
> files are transferred! luis, any luck reproducing my problems? i can
> give you ssh access to either of my boxes if you need it 8-).
>
> Thanks!
>
> Joseph Cheek
>
> Xaero wrote:
>
>> ok, I've made some more tests.
>> I discovered that if I use 20 Mhz frequency instead of "20/40"
>> frequency, the speed raises, about 3MB/s from router to the card. Is
>> it a known problem?
>>
>> Here is a screenshot of throughput speed using iperf:
>> http://dl.getdropbox.com/u/158338/benchmark_dlink.png
>>
>>
>
>
prev parent reply other threads:[~2009-01-21 5:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 0:56 [ath9k-devel] dwa-547 very slow Xaero
2009-01-20 19:22 ` Xaero
2009-01-20 19:23 ` Xaero
2009-01-20 19:48 ` Luis R. Rodriguez
2009-01-20 20:03 ` Joseph Cheek
2009-01-20 20:21 ` Luis R. Rodriguez
2009-01-20 20:37 ` [ath9k-devel] loss of connectivity after large file transfer Joseph Cheek
2009-01-20 21:11 ` Luis R. Rodriguez
2009-01-20 23:38 ` [ath9k-devel] dwa-547 very slow Xaero
2009-01-21 0:14 ` Luis R. Rodriguez
2009-01-21 1:50 ` Sujith
2009-01-21 5:14 ` Joseph Cheek [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=4976AF3F.1010705@cheek.com \
--to=joseph@cheek.com \
--cc=ath9k-devel@lists.ath9k.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.