From: "Lukáš Turek" <8an@praha12.net>
To: 海藻敬之 <tkaiso@thinktube.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] [PATCH 4/5] ath5k: Reimplement clock rate to usec conversion
Date: Sat, 26 Dec 2009 18:55:38 +0100 [thread overview]
Message-ID: <200912261855.42408.8an@praha12.net> (raw)
In-Reply-To: <4B32B76D.3090508@thinktube.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On 24.12.2009 01:35 海藻敬之 wrote:
> ( sorry again for my last post which was corrupted. I do not why... some
> coding issue.. please be patient. )
For some reason your client tries to send the mail in UTF-16 instead of UTF-8,
so mailserver cuts the mail at the zero byte in the first character of
message body.
> My work did not include "coverage class". I just applied [3/5], [4/5].
> Before applying [4/5], ath5k_hw_clocktoh() takes care of 11a but 11g/b,
> and your new ath5k_he_get_clockrate() handles both 11a and 11b/g, correct ?
> Therefore, I thought this can make difference in throughput. am I wrong
> on this point ?
But ath5k_hw_get_clockrate() is just a dead code until [5/5] is applied, and
even after applying [5/5] it's only called on set_coverage() path, so it
couldn't make any difference in your case.
> 3Mbps/TCP is so low, isn't it ? how long is it between the two nodes ?
It's 3 megabytes per seconds, not megabits, as reported by wget. I haven't
done any real throughput test with iperf yet, so your results might be more
correct, but they shouldn't depend on my patches.
Lukas Turek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next parent reply other threads:[~2009-12-26 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B32B76D.3090508@thinktube.com>
2009-12-26 17:55 ` Lukáš Turek [this message]
2009-12-23 11:43 [ath5k-devel] [PATCH 4/5] ath5k: Reimplement clock rate to usec conversion 海藻敬之
2009-12-23 13:54 ` Lukáš Turek
-- strict thread matches above, loose matches on Subject: below --
2009-12-15 17:56 [PATCH 0/5] Setting coverage class (and ACK timeout and slot time), take two Lukáš Turek
2009-12-15 17:56 ` [PATCH 4/5] ath5k: Reimplement clock rate to usec conversion Lukáš Turek
2009-12-21 10:26 ` [ath5k-devel] " 海藻敬之
2009-12-21 12:38 ` Lukáš Turek
[not found] ` <4B301FE9.2020702@thinktube.com>
2009-12-22 16:08 ` Lukáš Turek
[not found] ` <4B2F50DD.60701@thinktube.com>
2009-12-21 12:40 ` Lukáš Turek
2009-12-21 15:08 ` Bob Copeland
2009-12-21 15:28 ` Lukáš Turek
2009-12-22 3:28 ` Bob Copeland
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=200912261855.42408.8an@praha12.net \
--to=8an@praha12.net \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tkaiso@thinktube.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).