All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <BAE24CBF-416D-4665-B2C9-CE1F5EAE28FF@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index dddbbc9..6336ae2 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -41,18 +41,18 @@ for the RX/TX rings.
 > 2) higher level user-space frameworks which may want to use AF_XDP, 
 > such as DPDK, do not currently support having buffers with 'fixed' 
 > alignment.
->     The reason that DPDK uses arbitrary placement is that:
->         - it would stop things working on certain NICs which 
+> ??? The reason that DPDK uses arbitrary placement is that:
+> ??? ??? - it would stop things working on certain NICs which 
 > need the actual writable space specified in units of 1k - therefore we 
 > need 2k + metadata space.
->         - we place padding between buffers to avoid constantly 
+> ??? ??? - we place padding between buffers to avoid constantly 
 > hitting the same memory channels when accessing memory.
->         - it allows the application to choose the actual buffer 
+> ??? ??? - it allows the application to choose the actual buffer 
 > size it wants to use.
->     We make use of the above to allow us to speed up processing 
+> ??? We make use of the above to allow us to speed up processing 
 > significantly and also reduce the packet buffer memory size.
 >
->     Not having arbitrary buffer alignment also means an AF_XDP 
+> ??? Not having arbitrary buffer alignment also means an AF_XDP 
 > driver for DPDK cannot be a drop-in replacement for existing drivers 
 > in those frameworks. Even with a new capability to allow an arbitrary 
 > buffer alignment, existing apps will need to be modified to use that 
diff --git a/a/content_digest b/N1/content_digest
index ae8d4fe..b05a6c7 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -17,26 +17,13 @@
   "From\0Jonathan Lemon <jonathan.lemon\@gmail.com>\0"
 ]
 [
-  "Subject\0Re: [PATCH 00/11] XDP unaligned chunk placement support\0"
+  "Subject\0[Intel-wired-lan] [PATCH 00/11] XDP unaligned chunk placement support\0"
 ]
 [
   "Date\0Fri, 28 Jun 2019 13:29:02 -0700\0"
 ]
 [
-  "To\0Laatz",
-  " Kevin <kevin.laatz\@intel.com>\0"
-]
-[
-  "Cc\0Jakub Kicinski <jakub.kicinski\@netronome.com>",
-  " netdev\@vger.kernel.org",
-  " ast\@kernel.org",
-  " daniel\@iogearbox.net",
-  " bjorn.topel\@intel.com",
-  " magnus.karlsson\@intel.com",
-  " bpf\@vger.kernel.org",
-  " intel-wired-lan\@lists.osuosl.org",
-  " bruce.richardson\@intel.com",
-  " ciara.loftus\@intel.com\0"
+  "To\0intel-wired-lan\@osuosl.org\0"
 ]
 [
   "\0000:1\0"
@@ -88,18 +75,18 @@
   "> 2) higher level user-space frameworks which may want to use AF_XDP, \n",
   "> such as DPDK, do not currently support having buffers with 'fixed' \n",
   "> alignment.\n",
-  "> \302\240\302\240\302\240 The reason that DPDK uses arbitrary placement is that:\n",
-  "> \302\240\302\240\302\240 \302\240\302\240\302\240 - it would stop things working on certain NICs which \n",
+  "> ??? The reason that DPDK uses arbitrary placement is that:\n",
+  "> ??? ??? - it would stop things working on certain NICs which \n",
   "> need the actual writable space specified in units of 1k - therefore we \n",
   "> need 2k + metadata space.\n",
-  "> \302\240\302\240\302\240 \302\240\302\240\302\240 - we place padding between buffers to avoid constantly \n",
+  "> ??? ??? - we place padding between buffers to avoid constantly \n",
   "> hitting the same memory channels when accessing memory.\n",
-  "> \302\240\302\240\302\240 \302\240\302\240\302\240 - it allows the application to choose the actual buffer \n",
+  "> ??? ??? - it allows the application to choose the actual buffer \n",
   "> size it wants to use.\n",
-  "> \302\240\302\240\302\240 We make use of the above to allow us to speed up processing \n",
+  "> ??? We make use of the above to allow us to speed up processing \n",
   "> significantly and also reduce the packet buffer memory size.\n",
   ">\n",
-  "> \302\240\302\240\302\240 Not having arbitrary buffer alignment also means an AF_XDP \n",
+  "> ??? Not having arbitrary buffer alignment also means an AF_XDP \n",
   "> driver for DPDK cannot be a drop-in replacement for existing drivers \n",
   "> in those frameworks. Even with a new capability to allow an arbitrary \n",
   "> buffer alignment, existing apps will need to be modified to use that \n",
@@ -114,4 +101,4 @@
   "Jonathan"
 ]
 
-222c1cf46074a0255f80223961386fa5254300512bc2a7d958bc3d4b26bf76ce
+d90667615c8e033a11cbb10d1193b6fd3d1815be994358384130c25cc3180366
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.