aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/intel/igc
diff options
context:
space:
mode:
authorKui-Feng Lee <[email protected]>2023-04-21 21:41:31 +0000
committerDaniel Borkmann <[email protected]>2023-04-27 12:51:44 +0000
commit74fc8801edc279fb5f778eb91df48e4d3cd951a2 (patch)
tree0ae29c92bbaa4a7aa0b8a3d5c63a8a51e25126e6 /drivers/net/ethernet/intel/igc
parentdocs/bpf: Add LRU internals description and graph (diff)
downloadkernel-74fc8801edc279fb5f778eb91df48e4d3cd951a2.tar.gz
kernel-74fc8801edc279fb5f778eb91df48e4d3cd951a2.zip
bpftool: Show map IDs along with struct_ops links.
A new link type, BPF_LINK_TYPE_STRUCT_OPS, was added to attach struct_ops to links. (226bc6ae6405) It would be helpful for users to know which map is associated with the link. The assumption was that every link is associated with a BPF program, but this does not hold true for struct_ops. It would be better to display map_id instead of prog_id for struct_ops links. However, some tools may rely on the old assumption and need a prog_id. The discussion on the mailing list suggests that tools should parse JSON format. We will maintain the existing JSON format by adding a map_id without removing prog_id. As for plain text format, we will remove prog_id from the header line and add a map_id for struct_ops links. Signed-off-by: Kui-Feng Lee <[email protected]> Signed-off-by: Daniel Borkmann <[email protected]> Reviewed-by: Quentin Monnet <[email protected]> Acked-by: John Fastabend <[email protected]> Link: https://lore.kernel.org/bpf/[email protected]
Diffstat (limited to 'drivers/net/ethernet/intel/igc')
0 files changed, 0 insertions, 0 deletions