Commit | Line | Data |
---|---|---|
1aaa6ba3 NR |
1 | <!DOCTYPE html> |
2 | <html> | |
3 | <head> | |
4 | <meta http-equiv='content-type' content='text/html; charset=utf-8'> | |
5 | <meta name='viewport' content='width=device-width, initial-scale=1.0'> | |
6 | <style type='text/css'> | |
7 | body { margin: 1em 15%; } | |
8 | </style> | |
9 | </head> | |
10 | <body> | |
11 | <div class='story-header'> | |
c715ea02 | 12 | <h2><a href='0000764200.html'>[$] Writing network flow dissectors in BPF</a></h2> |
1aaa6ba3 NR |
13 | <div class='details'>([Kernel] Sep 6, 2018 15:59 UTC (Thu) (corbet))</div> |
14 | <br/> | |
15 | <div class='content' style='text-align: justify'> | |
e818d449 | 16 | 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.<br/><br/><br/><br/>[1] https://elixir.bootlin.com/linux/v4.18.6/source/net/core/flow_dissector.c<br/><br/>[2] https://lwn.net/Articles/763938/ |
1aaa6ba3 NR |
17 | </div> |
18 | <hr/> | |
19 | </div> | |
20 | </body> |