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
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
