X-Git-Url: http://git.nikiroo.be/?p=gofetch.git;a=blobdiff_plain;f=test%2Fexpected%2FLWN%2F0000764200.header.html;fp=test%2Fexpected%2FLWN%2F0000764200.header.html;h=655ac1e8ea531871c5d2e39d8a32db4aff52e90b;hp=cfcf95ab2820c26bd3887414c36483c57fe1a1ab;hb=3367f6256b5143b7cba2a61de36e74f389a5f379;hpb=b389651b0012a7ba1ff30d164958e155688ac216 diff --git a/test/expected/LWN/0000764200.header.html b/test/expected/LWN/0000764200.header.html index cfcf95a..655ac1e 100644 --- a/test/expected/LWN/0000764200.header.html +++ b/test/expected/LWN/0000764200.header.html @@ -9,11 +9,11 @@
-

[$] Writing network flow dissectors in BPF

+

[$] Writing network flow dissectors in BPF

([Kernel] Sep 6, 2018 15:59 UTC (Thu) (corbet))

- Network packet headers contain a great deal of information, but the kernel often only needs a subset of that information to be able to perform filtering or associate any given packet with a flow. The piece of code that follows the different layers of packet encapsulation to find the important data is called a flow dissector. In current Linux kernels, the flow dissector is written in C. A patch set has been proposed recently to implement it in BPF with the clear goal of improving security, flexibility, and maybe even performance. + Network packet headers contain a great deal of information, but the kernel often only needs a subset of that information to be able to perform filtering or associate any given packet with a flow. The piece of code that follows the different layers of packet encapsulation to find the important data is called a flow dissector. In current Linux kernels, the [1]flow dissector is written in C. A [2]patch set has been proposed recently to implement it in BPF with the clear goal of improving security, flexibility, and maybe even performance.



[1] https://elixir.bootlin.com/linux/v4.18.6/source/net/core/flow_dissector.c

[2] https://lwn.net/Articles/763938/