diff for duplicates of <492C808A.20403@openwrt.org> diff --git a/a/1.txt b/N1/1.txt index d7e62b3..ca626ee 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,19 +1,14 @@ Benoit PAPILLAULT wrote: -> Felix Fietkau a =E9crit : +> Felix Fietkau a écrit : >> While reading the code for calculating the frame duration, i noticed >> something odd: It doesn't seem to be taking into account the short ->> vs long preamble distinction for ERP rates. IMHO this might be causi= -ng ->> issues like this. I've seen similar behaviour a long time ago when t= -esting ->> iwl3945 against a Broadcom AP with exactly the same throughput drop = -(500- +>> vs long preamble distinction for ERP rates. IMHO this might be causing +>> issues like this. I've seen similar behaviour a long time ago when testing +>> iwl3945 against a Broadcom AP with exactly the same throughput drop (500- >> 600 kbits/s). ->> When I analyzed the problem with an extra monitor mode card, I found= - out ->> that the throughput drop is caused by a huge number of retransmissio= -ns, ->=20 +>> When I analyzed the problem with an extra monitor mode card, I found out +>> that the throughput drop is caused by a huge number of retransmissions, +> > In the test I've done, there was no retransmission at all (no > duplicates). I don't save a capture file, so I cannot tell for sure. Which test specifically? iwl3945 or ath5k? @@ -22,16 +17,10 @@ related. Please do make some logs of the throughput issue and then some more of the same kind of traffic without throughput issues (same card, same driver). -> What is the code computing frame duration you are referring to? How i= -t +> What is the code computing frame duration you are referring to? How it > could affect the hardware behavior? I looked at it again and now I don't think it's the cause anymore. I did some comparisons against other stacks/drivers and this part seems correct after all. - Felix --- -To unsubscribe from this list: send the line "unsubscribe linux-wireles= -s" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 484557c..cee17de 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -11,7 +11,7 @@ "To\0Benoit PAPILLAULT <benoit.papillault@free.fr>\0" "Cc\0Maxim Levitsky <maximlevitsky@gmail.com>" Derek Smithies <derek@indranet.co.nz> - ath5k-devel@lists.ath5k.org + ath5k-devel@venema.h4ckr.net linux-wireless@vger.kernel.org linux-kernel@vger.kernel.org ipw3945-devel@lists.sourceforge.net @@ -20,21 +20,16 @@ "\00:1\0" "b\0" "Benoit PAPILLAULT wrote:\n" - "> Felix Fietkau a =E9crit :\n" + "> Felix Fietkau a \303\251crit :\n" ">> While reading the code for calculating the frame duration, i noticed\n" ">> something odd: It doesn't seem to be taking into account the short\n" - ">> vs long preamble distinction for ERP rates. IMHO this might be causi=\n" - "ng\n" - ">> issues like this. I've seen similar behaviour a long time ago when t=\n" - "esting\n" - ">> iwl3945 against a Broadcom AP with exactly the same throughput drop =\n" - "(500-\n" + ">> vs long preamble distinction for ERP rates. IMHO this might be causing\n" + ">> issues like this. I've seen similar behaviour a long time ago when testing\n" + ">> iwl3945 against a Broadcom AP with exactly the same throughput drop (500-\n" ">> 600 kbits/s).\n" - ">> When I analyzed the problem with an extra monitor mode card, I found=\n" - " out\n" - ">> that the throughput drop is caused by a huge number of retransmissio=\n" - "ns,\n" - ">=20\n" + ">> When I analyzed the problem with an extra monitor mode card, I found out\n" + ">> that the throughput drop is caused by a huge number of retransmissions,\n" + "> \n" "> In the test I've done, there was no retransmission at all (no\n" "> duplicates). I don't save a capture file, so I cannot tell for sure.\n" "Which test specifically? iwl3945 or ath5k?\n" @@ -43,18 +38,12 @@ "some more of the same kind of traffic without throughput issues\n" "(same card, same driver).\n" "\n" - "> What is the code computing frame duration you are referring to? How i=\n" - "t\n" + "> What is the code computing frame duration you are referring to? How it\n" "> could affect the hardware behavior?\n" "I looked at it again and now I don't think it's the cause anymore. I\n" " did some comparisons against other stacks/drivers and this part\n" "seems correct after all.\n" "\n" - "- Felix\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-wireles=\n" - "s\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + - Felix -3819d1726b4d1b2e19a225df0345e55ba8c67a90bef14e43cb965f7631efb006 +a0daca2b7c011d3270539e57fc01d9b755317fb1183d48bc0df99e25ca356304
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.