diff for duplicates of <87tvnp9peg.fsf@toke.dk>

diff --git a/a/1.txt b/N1/1.txt
index d4a33a5..60ffdc2 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,7 +4,7 @@ Arend van Spriel <arend.vanspriel@broadcom.com> writes:
 >
 > On 8/10/2018 9:52 PM, Ben Greear wrote:
 >> On 08/10/2018 12:28 PM, Arend van Spriel wrote:
->>> On 8/10/2018 3:20 PM, Toke Høiland-Jørgensen wrote:
+>>> On 8/10/2018 3:20 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
 >>>> Arend van Spriel <arend.vanspriel@broadcom.com> writes:
 >>>>
 >>>>> On 8/8/2018 9:00 PM, Peter Oh wrote:
@@ -12,7 +12,8 @@ Arend van Spriel <arend.vanspriel@broadcom.com> writes:
 >>>>>>
 >>>>>> On 08/08/2018 03:40 AM, Wen Gong wrote:
 >>>>>>> Add a field for ath10k to adjust the sk_pacing_shift, mac80211 set
->>>>>>> the default value to 8, and ath10k will change it to 6. Then mac80211
+>>>>>>> the default value to 8, and ath10k will change it to 6. Then mac802=
+11
 >>>>>>> will use the changed value 6 as sk_pacing_shift since 6 is the best
 >>>>>>> value for tx throughput by test result.
 >>>>>> I don't think you can convince people with the numbers unless you
@@ -46,14 +47,14 @@ Arend van Spriel <arend.vanspriel@broadcom.com> writes:
 >>> I not sure either. Do you think a user could come up with something
 >>> like this (found here [1]):
 >>>
->>> sysctl -w net.core.rmem_max=8388608
->>> sysctl -w net.core.wmem_max=8388608
->>> sysctl -w net.core.rmem_default=65536
->>> sysctl -w net.core.wmem_default=65536
->>> sysctl -w net.ipv4.tcp_rmem='4096 87380 8388608'
->>> sysctl -w net.ipv4.tcp_wmem='4096 65536 8388608'
->>> sysctl -w net.ipv4.tcp_mem='8388608 8388608 8388608'
->>> sysctl -w net.ipv4.route.flush=1
+>>> sysctl -w net.core.rmem_max=3D8388608
+>>> sysctl -w net.core.wmem_max=3D8388608
+>>> sysctl -w net.core.rmem_default=3D65536
+>>> sysctl -w net.core.wmem_default=3D65536
+>>> sysctl -w net.ipv4.tcp_rmem=3D'4096 87380 8388608'
+>>> sysctl -w net.ipv4.tcp_wmem=3D'4096 65536 8388608'
+>>> sysctl -w net.ipv4.tcp_mem=3D'8388608 8388608 8388608'
+>>> sysctl -w net.ipv4.route.flush=3D1
 >>>
 >>> Now the page listing this config claims this is for use "on Linux 2.4+
 >>> for high-bandwidth applications". Beats me if it still is correct in
@@ -69,17 +70,19 @@ Arend van Spriel <arend.vanspriel@broadcom.com> writes:
 >>> work. Some static
 >>> table with entries for the different devices?
 >>
->> Some users are not going to care about latency, and for others, latency may
+>> Some users are not going to care about latency, and for others, latency =
+may
 >> be absolutely important and they don't care about bandwidth.
 >>
->> So, it should be tunable.  sysctl can support per network-device settings,
+>> So, it should be tunable.  sysctl can support per network-device setting=
+s,
 >> right?  Or, probably could use ethtool API to set a per-netdev value as
 >> well.
 >> That might be nice for other network devices as well, not just wifi.
 >
-> I was under the impression that the parameters are all global, but your 
-> statement made me look. I came across some references here [2] so I 
-> checked the kernel sources under net/ and found net/ipv4/devinet.c [3]. 
+> I was under the impression that the parameters are all global, but your=20
+> statement made me look. I came across some references here [2] so I=20
+> checked the kernel sources under net/ and found net/ipv4/devinet.c [3].=20
 > So that confirms it supports per-netdev settings.
 
 Yeah, I think that *if* this is to be made configurable, a per-netdev
@@ -95,8 +98,3 @@ have a lot of effect, so it is not very useful to expose, which makes it
 not worth the added configuration complexity...
 
 -Toke
-
-_______________________________________________
-ath10k mailing list
-ath10k@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/ath10k
diff --git a/a/content_digest b/N1/content_digest
index c16c316..5b68198 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -24,7 +24,7 @@
  ">\n"
  "> On 8/10/2018 9:52 PM, Ben Greear wrote:\n"
  ">> On 08/10/2018 12:28 PM, Arend van Spriel wrote:\n"
- ">>> On 8/10/2018 3:20 PM, Toke H\303\270iland-J\303\270rgensen wrote:\n"
+ ">>> On 8/10/2018 3:20 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:\n"
  ">>>> Arend van Spriel <arend.vanspriel@broadcom.com> writes:\n"
  ">>>>\n"
  ">>>>> On 8/8/2018 9:00 PM, Peter Oh wrote:\n"
@@ -32,7 +32,8 @@
  ">>>>>>\n"
  ">>>>>> On 08/08/2018 03:40 AM, Wen Gong wrote:\n"
  ">>>>>>> Add a field for ath10k to adjust the sk_pacing_shift, mac80211 set\n"
- ">>>>>>> the default value to 8, and ath10k will change it to 6. Then mac80211\n"
+ ">>>>>>> the default value to 8, and ath10k will change it to 6. Then mac802=\n"
+ "11\n"
  ">>>>>>> will use the changed value 6 as sk_pacing_shift since 6 is the best\n"
  ">>>>>>> value for tx throughput by test result.\n"
  ">>>>>> I don't think you can convince people with the numbers unless you\n"
@@ -66,14 +67,14 @@
  ">>> I not sure either. Do you think a user could come up with something\n"
  ">>> like this (found here [1]):\n"
  ">>>\n"
- ">>> sysctl -w net.core.rmem_max=8388608\n"
- ">>> sysctl -w net.core.wmem_max=8388608\n"
- ">>> sysctl -w net.core.rmem_default=65536\n"
- ">>> sysctl -w net.core.wmem_default=65536\n"
- ">>> sysctl -w net.ipv4.tcp_rmem='4096 87380 8388608'\n"
- ">>> sysctl -w net.ipv4.tcp_wmem='4096 65536 8388608'\n"
- ">>> sysctl -w net.ipv4.tcp_mem='8388608 8388608 8388608'\n"
- ">>> sysctl -w net.ipv4.route.flush=1\n"
+ ">>> sysctl -w net.core.rmem_max=3D8388608\n"
+ ">>> sysctl -w net.core.wmem_max=3D8388608\n"
+ ">>> sysctl -w net.core.rmem_default=3D65536\n"
+ ">>> sysctl -w net.core.wmem_default=3D65536\n"
+ ">>> sysctl -w net.ipv4.tcp_rmem=3D'4096 87380 8388608'\n"
+ ">>> sysctl -w net.ipv4.tcp_wmem=3D'4096 65536 8388608'\n"
+ ">>> sysctl -w net.ipv4.tcp_mem=3D'8388608 8388608 8388608'\n"
+ ">>> sysctl -w net.ipv4.route.flush=3D1\n"
  ">>>\n"
  ">>> Now the page listing this config claims this is for use \"on Linux 2.4+\n"
  ">>> for high-bandwidth applications\". Beats me if it still is correct in\n"
@@ -89,17 +90,19 @@
  ">>> work. Some static\n"
  ">>> table with entries for the different devices?\n"
  ">>\n"
- ">> Some users are not going to care about latency, and for others, latency may\n"
+ ">> Some users are not going to care about latency, and for others, latency =\n"
+ "may\n"
  ">> be absolutely important and they don't care about bandwidth.\n"
  ">>\n"
- ">> So, it should be tunable.  sysctl can support per network-device settings,\n"
+ ">> So, it should be tunable.  sysctl can support per network-device setting=\n"
+ "s,\n"
  ">> right?  Or, probably could use ethtool API to set a per-netdev value as\n"
  ">> well.\n"
  ">> That might be nice for other network devices as well, not just wifi.\n"
  ">\n"
- "> I was under the impression that the parameters are all global, but your \n"
- "> statement made me look. I came across some references here [2] so I \n"
- "> checked the kernel sources under net/ and found net/ipv4/devinet.c [3]. \n"
+ "> I was under the impression that the parameters are all global, but your=20\n"
+ "> statement made me look. I came across some references here [2] so I=20\n"
+ "> checked the kernel sources under net/ and found net/ipv4/devinet.c [3].=20\n"
  "> So that confirms it supports per-netdev settings.\n"
  "\n"
  "Yeah, I think that *if* this is to be made configurable, a per-netdev\n"
@@ -114,11 +117,6 @@
  "have a lot of effect, so it is not very useful to expose, which makes it\n"
  "not worth the added configuration complexity...\n"
  "\n"
- "-Toke\n"
- "\n"
- "_______________________________________________\n"
- "ath10k mailing list\n"
- "ath10k@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/ath10k
+ -Toke
 
-4476404e6dd5879199a8fc244c887a30112f1081cc3341f303f2598a4316532b
+865a97392fd4db6cf0b89e47e19e65a8d76e6103e68f8f1368b663d8103922e8
