summaryrefslogtreecommitdiffstats
path: root/tools/lguest
diff options
context:
space:
mode:
authorDaniel Borkmann2015-08-01 00:46:29 +0200
committerDavid S. Miller2015-08-03 02:20:47 +0200
commitba7591d8b28bd16a2eface5d009ab0b60c7629a4 (patch)
tree17f39a416a27698e437e523a02428cf9cbdf7720 /tools/lguest
parentbnx2x: Correct logic for pvid configuration. (diff)
downloadkernel-qcow2-linux-ba7591d8b28bd16a2eface5d009ab0b60c7629a4.tar.gz
kernel-qcow2-linux-ba7591d8b28bd16a2eface5d009ab0b60c7629a4.tar.xz
kernel-qcow2-linux-ba7591d8b28bd16a2eface5d009ab0b60c7629a4.zip
ebpf: add skb->hash to offset map for usage in {cls, act}_bpf or filters
Add skb->hash to the __sk_buff offset map, so it can be accessed from an eBPF program. We currently already do this for classic BPF filters, but not yet on eBPF, it might be useful as a demuxer in combination with helpers like bpf_clone_redirect(), toy example: __section("cls-lb") int ingress_main(struct __sk_buff *skb) { unsigned int which = 3 + (skb->hash & 7); /* bpf_skb_store_bytes(skb, ...); */ /* bpf_l{3,4}_csum_replace(skb, ...); */ bpf_clone_redirect(skb, which, 0); return -1; } I was thinking whether to add skb_get_hash(), but then concluded the raw skb->hash seems fine in this case: we can directly access the hash w/o extra eBPF helper function call, it's filled out by many NICs on ingress, and in case the entropy level would not be sufficient, people can still implement their own specific sw fallback hash mix anyway. Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Acked-by: Alexei Starovoitov <ast@plumgrid.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/lguest')
0 files changed, 0 insertions, 0 deletions