X-Git-Url: http://git.nikiroo.be/?a=blobdiff_plain;f=test%2Fexpected%2FLWN%2F0000764200.header;fp=test%2Fexpected%2FLWN%2F0000764200.header;h=9cd70e2caf882a63ce2a9126ccfb228e4fd5b6b0;hb=1aaa6ba3686a5a14f2957b6b8d02ffc0903f6832;hp=0000000000000000000000000000000000000000;hpb=a71d4075a8591b0655277b1a0e606ee48d228869;p=gofetch.git

diff --git a/test/expected/LWN/0000764200.header b/test/expected/LWN/0000764200.header
new file mode 100644
index 0000000..9cd70e2
--- /dev/null
+++ b/test/expected/LWN/0000764200.header
@@ -0,0 +1,13 @@
+0[$] Writing network flow dissectors in BPF	null/LWN/0000764200		70
+i  [Kernel] Sep 6, 2018 15:59 UTC (Thu) (corbet)
+i
+i    Network  packet  headers  contain  a great deal of information,
+i    but  the  kernel  often only needs a subset of that information
+i    to  be  able to perform filtering or associate any given packet
+i    with  a  flow.  The  piece  of  code that follows the different
+i    layers  of  packet  encapsulation to find the important data is
+i    called  a  flow  dissector.  In current Linux kernels, the flow
+i    dissector  is  written  in  C.  A  patch  set has been proposed
+i    recently  to  implement  it  in  BPF  with  the  clear  goal of
+i    improving security, flexibility, and maybe even performance.
+i