XDP Newbies
[Prev Page][Next Page]
- Re: [Intel-wired-lan] bpf_redirect and xdpgeneric
- Re: Using pinned maps within a network namespace
- Re: bpf_redirect and xdpgeneric
- Re: bpf_redirect and xdpgeneric
- From: Jesper Dangaard Brouer
- XDP/eBPF/jit problem, system crash, with some ctx access changes
- Call for Proposals: eBPF Summit 2020
- Re: Using pinned maps within a network namespace
- Re: NDv6 and xdp-filter
- From: Toke Høiland-Jørgensen
- Re: xdp-filter troubles
- NDv6 and xdp-filter
- Re: XDP program unloads by itself
- Re: XDP program unloads by itself
- From: Toke Høiland-Jørgensen
- XDP program unloads by itself
- Re: xdp-filter troubles
- From: Toke Høiland-Jørgensen
- Re: xdp-filter troubles
- Re: xdp-filter troubles
- From: Toke Høiland-Jørgensen
- [no subject]
- Re: bpf_redirect and xdpgeneric
- Re: bpf_redirect and xdpgeneric
- Re: bpf_redirect and xdpgeneric
- Re: bpf_redirect and xdpgeneric
- From: Toke Høiland-Jørgensen
- bpf_redirect and xdpgeneric
- Re: Using pinned maps within a network namespace
- Re: Using pinned maps within a network namespace
- Re: Using pinned maps within a network namespace
- Re: Using pinned maps within a network namespace
- Using pinned maps within a network namespace
- Another IP fragmentation question
- From: Alexander Petrovsky
- Re: Using XDP for Cloud VMs by David Ahern
- Re: Using XDP for Cloud VMs by David Ahern
- Re: Using XDP for Cloud VMs by David Ahern
- Using XDP for Cloud VMs by David Ahern
- From: Jesper Dangaard Brouer
- Re: Kernel Panic when loading XDP on i40e driver
- Re: Kernel Panic when loading XDP on i40e driver
- Adding xdp-newbies to lore.kernel.org
- From: Toke Høiland-Jørgensen
- Re: XDP and AF_XDP
- From: Toke Høiland-Jørgensen
- XDP and AF_XDP
- From: Michael A. Flückiger
- Re: Kernel Panic when loading XDP on i40e driver
- Kernel Panic when loading XDP on i40e driver
- Re: Clang target bpf compile issue/fail on Ubuntu and Debian
- taking first steps with XDP
- [FINAL REMINDER] LPC 2020 Networking and BPF Track CFP
- Clang target bpf compile issue/fail on Ubuntu and Debian
- From: Jesper Dangaard Brouer
- Re: igb native xdp support
- igb native xdp support
- LPC 2020 Networking and BPF Track CFP (Reminder)
- Re: IP fragmentation
- Re: IP fragmentation
- From: Alexander Petrovsky
- Re: IP fragmentation
- IP fragmentation
- From: Alexander Petrovsky
- Re: XDP Software Issue - Payload Matching
- From: Toke Høiland-Jørgensen
- Re: XDP Software Issue - Payload Matching
- Re: TCP Payload
- From: Toke Høiland-Jørgensen
- TCP Payload
- LPC 2020 Networking and BPF Track CFP
- Re: Talk about AF_XDP support multithread concurrently receive packet
- Re: Talk about AF_XDP support multithread concurrently receive packet
- Re: CQ error on CQN 0x43e, syndrome 0x1
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: CQ error on CQN 0x43e, syndrome 0x1
- From: Jesper Dangaard Brouer
- CQ error on CQN 0x43e, syndrome 0x1
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: Lightweight packet timestamping
- Re: Lightweight packet timestamping
- Re: Lightweight packet timestamping
- From: Jesper Dangaard Brouer
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- Re: [iovisor-dev] Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- From: Jesper Dangaard Brouer
- Re: Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- From: Toke Høiland-Jørgensen
- Re: Lightweight packet timestamping
- From: Toke Høiland-Jørgensen
- Re: Error loading xdp program that worked with bpf_load
- Re: Error loading xdp program that worked with bpf_load
- From: Toke Høiland-Jørgensen
- Error loading xdp program that worked with bpf_load
- Re: Lightweight packet timestamping
- Re: How to load BTF style maps?
- From: Toke Høiland-Jørgensen
- How to load BTF style maps?
- Re: Lightweight packet timestamping
- Re: Intel X520 looses ethtool flow-type rule the moment a BPF / XDP program is loaded
- AW: Intel X520 looses ethtool flow-type rule the moment a BPF / XDP program is loaded
- Re: Intel X520 looses ethtool flow-type rule the moment a BPF / XDP program is loaded
- AW: Intel X520 looses ethtool flow-type rule the moment a BPF / XDP program is loaded
- Re: Intel X520 looses ethtool flow-type rule the moment a BPF / XDP program is loaded
- Re: XDP_REDIRECT with xsks_map and dev_map
- Re: XDP_REDIRECT with xsks_map and dev_map
- Intel X520 looses ethtool flow-type rule the moment a BPF / XDP program is loaded
- Re: XDP_REDIRECT with xsks_map and dev_map
- From: Toke Høiland-Jørgensen
- AW: Intel 10G 2P X520 Adapter doesn't receive anything with AF XDP
- Re: XDP_REDIRECT with xsks_map and dev_map
- Intel 10G 2P X520 Adapter doesn't receive anything with AF XDP
- Lightweight packet timestamping
- Re: Dynamically adding new multicast streams
- AW: Dynamically adding new multicast streams
- Re: Dynamically adding new multicast streams
- Dynamically adding new multicast streams
- Re: XDP_REDIRECT with xsks_map and dev_map
- From: Toke Høiland-Jørgensen
- Re: XDP_REDIRECT with xsks_map and dev_map
- Re: XDP_REDIRECT with xsks_map and dev_map
- Re: XDP_REDIRECT with xsks_map and dev_map
- From: Toke Høiland-Jørgensen
- Re: XDP_REDIRECT with xsks_map and dev_map
- Re: XDP_REDIRECT with xsks_map and dev_map
- From: Toke Høiland-Jørgensen
- Re: XDP_REDIRECT with xsks_map and dev_map
- Re: XDP_REDIRECT with xsks_map and dev_map
- From: Toke Høiland-Jørgensen
- Re: XDP_REDIRECT with xsks_map and dev_map
- Re: XDP_REDIRECT with xsks_map and dev_map
- From: Toke Høiland-Jørgensen
- XDP_REDIRECT with xsks_map and dev_map
- Re: fentry/fexit trace to BPF_PROG_TYPE_EXT BPF program not working
- Re: fentry/fexit trace to BPF_PROG_TYPE_EXT BPF program not working
- Re: XDP_REDIRECT forwarding speed
- Re: XDP_REDIRECT forwarding speed
- From: Jesper Dangaard Brouer
- XDP_REDIRECT forwarding speed
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- Re: AF_XDP Side Of Project Breaking With XDP-Native
- From: Jesper Dangaard Brouer
- AF_XDP Side Of Project Breaking With XDP-Native
- Re: XDP Software Issue - Payload Matching
- From: Toke Høiland-Jørgensen
- Re: XDP Software Issue - Payload Matching
- Re: XDP_PASS and XDP_REDIRECT
- From: Toke Høiland-Jørgensen
- XDP_PASS and XDP_REDIRECT
- Re: How does the Kernel decide which Umem frame to choose for the next packet?
- AW: How does the Kernel decide which Umem frame to choose for the next packet?
- Re: How does the Kernel decide which Umem frame to choose for the next packet?
- How does the Kernel decide which Umem frame to choose for the next packet?
- Re: Under which circumstances does `xsk_ring_prod__reserve` return 0?
- Under which circumstances does `xsk_ring_prod__reserve` return 0?
- Re: fentry/fexit trace to BPF_PROG_TYPE_EXT BPF program not working
- Re: fentry/fexit trace to BPF_PROG_TYPE_EXT BPF program not working
- Re: XDP Software Issue - Payload Matching
- From: Toke Høiland-Jørgensen
- Re: XDP Software Issue - Payload Matching
- Re: XDP Software Issue - Payload Matching
- From: Toke Høiland-Jørgensen
- Re: XDP Software Issue - Payload Matching
- Re: XDP Software Issue - Payload Matching
- From: Toke Høiland-Jørgensen
- XDP Software Issue - Payload Matching
- Re: Fighting BPF verifier to reach end-of-packet with XDP
- Re: Fighting BPF verifier to reach end-of-packet with XDP
- From: Jesper Dangaard Brouer
- Re: fentry/fexit trace to BPF_PROG_TYPE_EXT BPF program not working
- Seeking candidates for PhD position related to XDP/eBPF
- From: Jesper Dangaard Brouer
- Re: XDP Native mode with public cloud (GCP)
- fentry/fexit trace to BPF_PROG_TYPE_EXT BPF program not working
- Re: XDP Native mode with public cloud (GCP)
- Re: XDP Native mode with public cloud (GCP)
- Re: XDP Native mode with public cloud (GCP)
- XDP Native mode with public cloud (GCP)
- Re: Difference in TCP throughput in comparison to OVS
- From: Toke Høiland-Jørgensen
- Difference in TCP throughput in comparison to OVS
- Re: Error creating a AF_XDP socket after deleting
- Re: building eBPF
- Re: building eBPF
- Re: building eBPF
- From: Toke Høiland-Jørgensen
- Re: building eBPF
- From: Jesper Dangaard Brouer
- Re: Error creating a AF_XDP socket after deleting
- Re: building eBPF
- Re: Error creating a AF_XDP socket after deleting
- Error creating a AF_XDP socket after deleting
- Re: building eBPF
- Re: building eBPF
- Re: building eBPF
- From: Jesper Dangaard Brouer
- virtio and XDP: How to do flow steering + shared umem
- Re: Running XSK on a tun device
- Re: Running XSK on a tun device
- Re: Running XSK on a tun device
- Running XSK on a tun device
- Re: Using AF_XDP To Modify Outgoing Packets
- Re: Using AF_XDP To Modify Outgoing Packets
- From: Jesper Dangaard Brouer
- Re: Using AF_XDP To Modify Outgoing Packets
- From: Toke Høiland-Jørgensen
- Re: Using AF_XDP To Modify Outgoing Packets
- Re: Using AF_XDP To Modify Outgoing Packets
- From: Toke Høiland-Jørgensen
- Re: Using AF_XDP To Modify Outgoing Packets
- Re: Using AF_XDP To Modify Outgoing Packets
- Re: Using AF_XDP To Modify Outgoing Packets
- Using AF_XDP To Modify Outgoing Packets
- Is there a way to process multiple shared umem sockets on same RX-queue in parallel?
- Re: Shared Umem and reducing ksoftirqd-Load
- AW: Shared Umem and reducing ksoftirqd-Load
- Re: Shared Umem and reducing ksoftirqd-Load
- AW: Shared Umem and reducing ksoftirqd-Load
- Re: Shared Umem and reducing ksoftirqd-Load
- AW: Shared Umem and reducing ksoftirqd-Load
- Re: Shared Umem and reducing ksoftirqd-Load
- AW: Shared Umem and reducing ksoftirqd-Load
- Re: Shared Umem and reducing ksoftirqd-Load
- Shared Umem and reducing ksoftirqd-Load
- Is there a problem with UDP-packets of size 371 bytes and less?
- AW: Why does my AF-XDP Socket lose packets whereas a generic linux socket doesn't?
- Re: Why does my AF-XDP Socket lose packets whereas a generic linux socket doesn't?
- From: Jesper Dangaard Brouer
- Why does my AF-XDP Socket lose packets whereas a generic linux socket doesn't?
- AW: Shared Umem between processes
- AW: Shared Umem between processes
- Re: Shared Umem between processes
- Re: Shared Umem between processes
- From: Toke Høiland-Jørgensen
- Re: Shared Umem between processes
- AW: Shared Umem between processes
- Re: Shared Umem between processes
- AW: Shared Umem between processes
- Re: Shared Umem between processes
- AW: Shared Umem between processes
- Re: Shared Umem between processes
- Re: xdpsock poll syscall CPU 100%
- Re: xdpsock poll syscall CPU 100%
- Re: xdpsock poll syscall CPU 100%
- Re: xdpsock poll syscall CPU 100%
- Re: xdpsock poll syscall CPU 100%
- Re: xdpsock poll syscall CPU 100%
- Re: xdpsock poll syscall CPU 100%
- xdpsock poll syscall CPU 100%
- Re: Capture xdp packets in an fentry BPF hook
- Re: Capture xdp packets in an fentry BPF hook
- From: Toke Høiland-Jørgensen
- Re: Capture xdp packets in an fentry BPF hook
- Re: Capture xdp packets in an fentry BPF hook
- From: Toke Høiland-Jørgensen
- Re: Capture xdp packets in an fentry BPF hook
- Capture xdp packets in an fentry BPF hook
- Re: Doing a bpf trace of an XDP bpf program using bpf_perf_event_output()
- Re: Need a way to modify the section name for a read program object
- From: Toke Høiland-Jørgensen
- Re: Need a way to modify the section name for a read program object
- Doing a bpf trace of an XDP bpf program using bpf_perf_event_output()
- Re: [PATCH bpf] xsk: publish global consumer pointers when NAPI is finsihed
- Re: [PATCH bpf] xsk: publish global consumer pointers when NAPI is finsihed
- Re: [PATCH bpf] xsk: publish global consumer pointers when NAPI is finsihed
- Re: [PATCH bpf] xsk: publish global consumer pointers when NAPI is finsihed
- Re: [PATCH bpf] xsk: publish global consumer pointers when NAPI is finsihed
- [PATCH bpf] xsk: publish global consumer pointers when NAPI is finsihed
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: zero-copy between interfaces
- Re: Need a way to modify the section name for a read program object
- Re: Need a way to modify the section name for a read program object
- From: Toke Høiland-Jørgensen
- Re: Need a way to modify the section name for a read program object
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: zero-copy between interfaces
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: Need a way to modify the section name for a read program object
- From: Toke Høiland-Jørgensen
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: Cannot run multiple 'xdpsock' concurrently?
- Re: Packets randomly dropped with virtio-net with xdp loaded in native mode
- Re: Packets randomly dropped with virtio-net with xdp loaded in native mode
- Packets randomly dropped with virtio-net with xdp loaded in native mode
- Cannot run multiple 'xdpsock' concurrently?
- Need a way to modify the section name for a read program object
- Re: Measuring/Debugging XDP Performance
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- RE: zero-copy between interfaces
- Re: xdpsock ... -N -z and AF_XDP XDP_ZEROCOPY not working: RESOLVED!
- From: Jesper Dangaard Brouer
- Re: xdpsock ... -N -z and AF_XDP XDP_ZEROCOPY not working: RESOLVED!
- xdpsock ... -N -z and AF_XDP XDP_ZEROCOPY not working: RESOLVED!
- Re: Measuring/Debugging XDP Performance
- From: Jesper Dangaard Brouer
- Re: Measuring/Debugging XDP Performance
- From: Jesper Dangaard Brouer
- Re: Maximum xdpsock txpush rate with AF_XDP ??
- Re: Maximum xdpsock txpush rate with AF_XDP ??
- Re: Measuring/Debugging XDP Performance
- From: Matheus Salgueiro Castanho
- Re: Measuring/Debugging XDP Performance
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: Maximum xdpsock txpush rate with AF_XDP ??
- Maximum xdpsock txpush rate with AF_XDP ??
- Re: zero-copy between interfaces
- Re: Measuring/Debugging XDP Performance
- Re: Measuring/Debugging XDP Performance
- From: Jesper Dangaard Brouer
- Re: Measuring/Debugging XDP Performance
- Re: Measuring/Debugging XDP Performance
- From: Jesper Dangaard Brouer
- Re: Measuring/Debugging XDP Performance
- From: Jesper Dangaard Brouer
- Re: Measuring/Debugging XDP Performance
- Re: zero-copy between interfaces
- Measuring/Debugging XDP Performance
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- From: Jesper Dangaard Brouer
- Re: XDP invalid memory access
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: XDP invalid memory access
- From: Toke Høiland-Jørgensen
- Re: zero-copy between interfaces
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: zero-copy between interfaces
- Re: XDP invalid memory access
- From: Toke Høiland-Jørgensen
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: zero-copy between interfaces
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- Re: XDP invalid memory access
- From: Toke Høiland-Jørgensen
- XDP invalid memory access
- Transmitting packets with AF_XDP on lo iface
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- AF_XDP with Rust
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- From: Toke Høiland-Jørgensen
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- From: Toke Høiland-Jørgensen
- Re: zero-copy between interfaces
- From: Jesper Dangaard Brouer
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- Re: zero-copy between interfaces
- From: Jesper Dangaard Brouer
- Re: zero-copy between interfaces
- From: Toke Høiland-Jørgensen
- Re: zero-copy between interfaces
- zero-copy between interfaces
- Re: Trying the bpf trace a bpf xdp program
- Re: AF_XDP headroom
- AF_XDP headroom
- XDP/AF_XDP checksum use case in OVS
- RE: bpf_csum_diff - R3 offset is outside of the packet
- From: Francesco Ruta (fruta)
- Re: Trying the bpf trace a bpf xdp program
- Re: bpf_csum_diff - R3 offset is outside of the packet
- bpf_csum_diff - R3 offset is outside of the packet
- From: Francesco Ruta (fruta)
- Re: Possible race condition on xsk_socket__create/xsk_bind
- Re: Trying the bpf trace a bpf xdp program
- Re: Possible race condition on xsk_socket__create/xsk_bind
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: xdpsock poll with 5.2.21rt kernel
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: xdpsock poll with 5.2.21rt kernel
- From: Sebastian Andrzej Siewior
- Re: xdpsock poll with 5.2.21rt kernel
- Re: Trying the bpf trace a bpf xdp program
- Re: xdpsock poll with 5.2.21rt kernel
- From: Sebastian Andrzej Siewior
- Re: Trying the bpf trace a bpf xdp program
- Video for understanding eBPF conceptually
- From: Jesper Dangaard Brouer
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Re: Trying the bpf trace a bpf xdp program
- Trying the bpf trace a bpf xdp program
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- From: Toke Høiland-Jørgensen
- Re: XDP - Bridge - not redirecting all UDP
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- From: Jesper Dangaard Brouer
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- Re: Access Hardware Timestamp in eBPF Program
- From: Toke Høiland-Jørgensen
- Re: error loading xdp program on virtio nic
- Re: Access Hardware Timestamp in eBPF Program
- Access Hardware Timestamp in eBPF Program
- XDP - Bridge - not redirecting all UDP
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- From: Jesper Dangaard Brouer
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- Re: error loading xdp program on virtio nic
- error loading xdp program on virtio nic
- xdpsock poll with 5.2.21rt kernel
- Re: xdp with mlx5 not working as expected
- xdp with mlx5 not working as expected
- Re: bpf_helpers and you... some more...
- From: Toke Høiland-Jørgensen
- bpf_helpers and you... some more...
- Re: bidirectional: => AF_XDP , <= XDP_REDIRECT
- Re: bidirectional: => AF_XDP , <= XDP_REDIRECT
- From: Jesper Dangaard Brouer
- Re: bidirectional: => AF_XDP , <= XDP_REDIRECT
- Useful request_id concept for bpf_debug_printk
- Re: sharing a simple ebpf code sample
- Re: sharing a simple ebpf code sample
- Re: How to debug XDP_REDIRECT errors
- From: Jesper Dangaard Brouer
- How to debug XDP_REDIRECT errors
- Re: sharing a simple ebpf code sample
- sharing a simple ebpf code sample
- Re: i40e: Kernel freezes with XDP_ZEROCOPY
- Re: i40e: Kernel freezes with XDP_ZEROCOPY
- Re: i40e: Kernel freezes with XDP_ZEROCOPY
- Re: i40e: Kernel freezes with XDP_ZEROCOPY
- Re: i40e: Kernel freezes with XDP_ZEROCOPY
- Re: i40e: Kernel freezes with XDP_ZEROCOPY
- Re: [PATCH] samples/bpf: make xdp_monitor use raw_tracepoints
- Re: [PATCH] samples/bpf: make xdp_monitor use raw_tracepoints
- From: Jesper Dangaard Brouer
- Re: [PATCH] samples/bpf: make xdp_monitor use raw_tracepoints
- Re: [PATCH] samples/bpf: make xdp_monitor use raw_tracepoints
- Re: XDP performance and benchmarks on generic not supported NICs
- XDP performance and benchmarks on generic not supported NICs
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- RE: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: [PATCH] samples/bpf: make xdp_monitor use raw_tracepoints
- From: Jesper Dangaard Brouer
- Re: Unable to run eBPF program that uses maps
- From: Toke Høiland-Jørgensen
- Unable to run eBPF program that uses maps
- [PATCH] samples/bpf: make xdp_monitor use raw_tracepoints
- Re: samples/bpf not working?
- Re: samples/bpf not working?
- Re: samples/bpf not working?
- samples/bpf not working?
- Re: xdpsock problem testing multiple queues
- RE: xdpsock problem testing multiple queues
- Re: xdpsock problem testing multiple queues
- Re: xdpsock problem testing multiple queues
- Re: xdpsock problem testing multiple queues
- xdpsock problem testing multiple queues
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: bug in AF_XDP socket cleanup?
- Re: bug? or how to properly clean up AF_XDP socket
- Re: bug in AF_XDP socket cleanup?
- Re: [xdp-tutorial] : permission denied when I try to execute a program
- Re: [xdp-tutorial] : permission denied when I try to execute a program
- Re: [xdp-tutorial] : permission denied when I try to execute a program
- bug? or how to properly clean up AF_XDP socket
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- [xdp-tutorial] : permission denied when I try to execute a program
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- RE: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- RE: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- RE: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: BUG: sleeping function called from invalid context in tcf_chain0_head_change_cb_del
- Re: BUG: sleeping function called from invalid context in tcf_chain0_head_change_cb_del
- Re: BUG: sleeping function called from invalid context in tcf_chain0_head_change_cb_del
- Re: BUG: sleeping function called from invalid context in tcf_chain0_head_change_cb_del
- BUG: sleeping function called from invalid context in tcf_chain0_head_change_cb_del
- Re: bidirectional: => AF_XDP , <= XDP_REDIRECT
- From: Toke Høiland-Jørgensen
- Re: bidirectional: => AF_XDP , <= XDP_REDIRECT
- Re: bidirectional: => AF_XDP , <= XDP_REDIRECT
- From: Toke Høiland-Jørgensen
- bidirectional: => AF_XDP , <= XDP_REDIRECT
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: [PATCH v3] virtio-net: lower min ring num_free for efficiency
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- From: Jesper Dangaard Brouer
- Re: net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- RE: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- Re: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- RE: AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- AF_XDP integration with FDio VPP? (Was: Questions about XDP)
- From: Jesper Dangaard Brouer
- Re: l2fwd between interfaces
- l2fwd between interfaces
- Re: [PATCH bpf-next v2 0/3] xdpsock: allow mmap2 usage for 32bits
- Re: [PATCH bpf-next] xsk: proper socket state check in xsk_poll
- Re: [PATCH bpf-next] xsk: proper socket state check in xsk_poll
- Re: [PATCH bpf-next] xsk: proper socket state check in xsk_poll
- [PATCH bpf-next] xsk: proper socket state check in xsk_poll
- Re: general protection fault in xsk_poll
- general protection fault in xsk_poll
- Re: [PATCH bpf-next v2 3/3] samples: bpf: syscal_nrs: use mmap2 if defined
- Re: [PATCH v2] virtio-net: lower min ring num_free for efficiency
- Re: WARNING in is_bpf_text_address
- Re: WARNING in is_bpf_text_address
- Re: [PATCH bpf-next v2 1/3] libbpf: use LFS (_FILE_OFFSET_BITS) instead of direct mmap2 syscall
- Re: [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Re: [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Re: [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Re: [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Oddly low CPU util during XDP_DROP
- [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- [PATCH bpf-next v2 1/3] libbpf: use LFS (_FILE_OFFSET_BITS) instead of direct mmap2 syscall
- [PATCH bpf-next v2 0/3] xdpsock: allow mmap2 usage for 32bits
- [PATCH bpf-next v2 3/3] samples: bpf: syscal_nrs: use mmap2 if defined
- Re: [PATCH v2] virtio-net: lower min ring num_free for efficiency
- Re: [PATCH] virtio-net: lower min ring num_free for efficiency
- Re: [PATCH] virtio-net: lower min ring num_free for efficiency
- Re: WARNING in is_bpf_text_address
- Re: [PATCH] virtio-net: lower min ring num_free for efficiency
- Re: [PATCH] virtio-net: lower min ring num_free for efficiency
- Re: [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 3/3] samples: bpf: syscal_nrs: use mmap2 if defined
- Re: [PATCH bpf-next 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Re: [PATCH bpf-next 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Re: [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- Re: [PATCH bpf-next 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- Re: [PATCH bpf-next 3/3] samples: bpf: syscal_nrs: use mmap2 if defined
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- [PATCH bpf-next 1/3] libbpf: add asm/unistd.h to xsk to get __NR_mmap2
- [PATCH bpf-next 3/3] samples: bpf: syscal_nrs: use mmap2 if defined
- [PATCH bpf-next 2/3] xdp: xdp_umem: replace kmap on vmap for umem map
- [PATCH bpf-next 0/3] xdpsock: allow mmap2 usage for 32bits
- Re: [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- Re: [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- Re: libbpf expected backward compatibility
- Re: [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- Re: libbpf expected backward compatibility
- libbpf expected backward compatibility
- Re: [PATCH v2 2/2] Documentation: sphinx: Don't parse socket() as identifier reference
- From: Mauro Carvalho Chehab
- [PATCH v2 2/2] Documentation: sphinx: Don't parse socket() as identifier reference
- From: Jonathan Neuschäfer
- Re: [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- [PATCH v2 bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- [PATCH bpf-next] mm: mmap: increase sockets maximum memory size pgoff for 32bits
- Re: [PATCH] Documentation/networking/af_xdp: Inhibit reference to struct socket
- From: Jonathan Neuschäfer
- Re: WARNING in is_bpf_text_address
- Re: [PATCH] Documentation/networking/af_xdp: Inhibit reference to struct socket
- [PATCH] Documentation/networking/af_xdp: Inhibit reference to struct socket
- From: Jonathan Neuschäfer
- Re: [PATCH v2 bpf-next] xdp: xdp_umem: fix umem pages mapping for 32bits systems
- Re: [bpf-next PATCH 0/3] bpf: improvements to xdp_fwd sample
- [PATCH v2 bpf-next] xdp: xdp_umem: fix umem pages mapping for 32bits systems
- Re: [bpf-next PATCH 0/3] bpf: improvements to xdp_fwd sample
- From: Jesper Dangaard Brouer
- Re: [bpf-next PATCH 2/3] samples/bpf: make xdp_fwd more practically usable via devmap lookup
- From: Jesper Dangaard Brouer
- Re: [bpf-next PATCH 0/3] bpf: improvements to xdp_fwd sample
- i40e: Kernel freezes with XDP_ZEROCOPY
- Re: [bpf-next PATCH 3/3] samples/bpf: xdp_fwd explain bpf_fib_lookup return codes
- Re: [bpf-next PATCH 2/3] samples/bpf: make xdp_fwd more practically usable via devmap lookup
- Re: [bpf-next PATCH 3/3] samples/bpf: xdp_fwd explain bpf_fib_lookup return codes
- Re: [bpf-next PATCH 1/3] samples/bpf: xdp_fwd rename devmap name to be xdp_tx_ports
- Re: [bpf-next PATCH 2/3] samples/bpf: make xdp_fwd more practically usable via devmap lookup
- Re: [bpf-next PATCH 1/3] samples/bpf: xdp_fwd rename devmap name to be xdp_tx_ports
- Re: [bpf-next PATCH 0/3] bpf: improvements to xdp_fwd sample
- From: Jesper Dangaard Brouer
- net/mlx5e: bind() always returns EINVAL with XDP_ZEROCOPY
- [bpf-next PATCH 3/3] samples/bpf: xdp_fwd explain bpf_fib_lookup return codes
- From: Jesper Dangaard Brouer
- [bpf-next PATCH 2/3] samples/bpf: make xdp_fwd more practically usable via devmap lookup
- From: Jesper Dangaard Brouer
- [bpf-next PATCH 1/3] samples/bpf: xdp_fwd rename devmap name to be xdp_tx_ports
- From: Jesper Dangaard Brouer
- [bpf-next PATCH 0/3] bpf: improvements to xdp_fwd sample
- From: Jesper Dangaard Brouer
- Re: [net v1 PATCH 0/4] net: fix regressions for generic-XDP
- Re: [net v1 PATCH 4/4] net: fix bpf_xdp_adjust_head regression for generic-XDP
- Re: Ajusting XSKMAP max_entries value
- Re: [net v1 PATCH 4/4] net: fix bpf_xdp_adjust_head regression for generic-XDP
- From: Jesper Dangaard Brouer
- Re: [net v1 PATCH 4/4] net: fix bpf_xdp_adjust_head regression for generic-XDP
- Re: xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- Re: xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- From: Jesper Dangaard Brouer
- [net v1 PATCH 4/4] net: fix bpf_xdp_adjust_head regression for generic-XDP
- From: Jesper Dangaard Brouer
- [net v1 PATCH 3/4] selftests/bpf: reduce time to execute test_xdp_vlan.sh
- From: Jesper Dangaard Brouer
- [net v1 PATCH 2/4] selftests/bpf: add wrapper scripts for test_xdp_vlan.sh
- From: Jesper Dangaard Brouer
- [net v1 PATCH 1/4] bpf: fix XDP vlan selftests test_xdp_vlan.sh
- From: Jesper Dangaard Brouer
- [net v1 PATCH 0/4] net: fix regressions for generic-XDP
- From: Jesper Dangaard Brouer
- Re: xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- Re: xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- From: Jesper Dangaard Brouer
- Re: xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- From: Jesper Dangaard Brouer
- Re: xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- From: Jesper Dangaard Brouer
- xdpgeneric, XDP_PASS, and bpf_xdp_adjust_head decapsulation dropping packets
- Ajusting XSKMAP max_entries value
- Re: Intel 800 series 100Gbe NIC with XDP
- From: Venkataramanan, Anirudh
- Re: Intel 800 series 100Gbe NIC with XDP
- From: Jesper Dangaard Brouer
- Intel 800 series 100Gbe NIC with XDP
- Re: [PATCH net-next] MAINTAINERS: Remove mailing-list entry for XDP (eXpress Data Path)
- Re: [PATCH net-next] MAINTAINERS: Remove mailing-list entry for XDP (eXpress Data Path)
- [PATCH net-next] MAINTAINERS: Remove mailing-list entry for XDP (eXpress Data Path)
- From: Jesper Dangaard Brouer
- Re: Should we remove xdp-newbies from kernel patch CC-list?
- From: Jesper Dangaard Brouer
- KASAN: use-after-free Read in bpf_get_prog_name
- [PATCH bpf] libbpf: fix using uninitialized ioctl results
- Re: [PATCH] [net-next] net/mlx5e: xsk: dynamically allocate mlx5e_channel_param
- Re: [PATCH] [net-next] net/mlx5e: xsk: dynamically allocate mlx5e_channel_param
- Re: AF_XDP and packet timestamp
- From: Jesper Dangaard Brouer
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- Re: [PATCH] virtio-net: parameterize min ring num_free for virtio receive
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- [PATCH AUTOSEL 5.2 175/249] xsk: Properly terminate assignment in xskq_produce_flush_desc
- [PATCH AUTOSEL 5.2 189/249] net/mlx5e: Attach/detach XDP program safely
- [PATCH AUTOSEL 4.19 114/158] xsk: Properly terminate assignment in xskq_produce_flush_desc
- [PATCH AUTOSEL 5.1 218/219] xdp: fix race on generic receive path
- [PATCH AUTOSEL 5.1 154/219] xsk: Properly terminate assignment in xskq_produce_flush_desc
- [PATCH AUTOSEL 5.2 248/249] xdp: fix race on generic receive path
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- [PATCH] mm/gup: Use put_user_page*() instead of put_page*()
- Re: [bpf-next v3 11/12] selftests/bpf: Add tests for bpf_prog_test_run for perf events progs
- Re: [bpf-next v3 11/12] selftests/bpf: Add tests for bpf_prog_test_run for perf events progs
- Re: [bpf-next v3 02/12] selftests/bpf: Avoid a clobbering of errno
- Linux Plumbers BPF micro-conference CFP (reminder)
- Re: [PATCH bpf] xdp: fix potential deadlock on socket mutex
- Re: [PATCH bpf] xdp: fix possible cq entry leak
- Re: x710 Checksum Offloading with XDP
- From: Toke Høiland-Jørgensen
- Re: [bpf-next v3 02/12] selftests/bpf: Avoid a clobbering of errno
- Re: [bpf-next v3 11/12] selftests/bpf: Add tests for bpf_prog_test_run for perf events progs
- Re: [bpf-next v3 08/12] tools headers: Sync struct bpf_perf_event_data
- Re: [bpf-next v3 07/12] tools headers: Adopt compiletime_assert from kernel sources
- Re: [bpf-next v3 01/12] selftests/bpf: Print a message when tester could not run a program
- x710 Checksum Offloading with XDP
- Re: [bpf-next v3 10/12] bpf: Implement bpf_prog_test_run for perf event programs
- Re: [bpf-next v3 09/12] bpf: Split out some helper functions
- Re: [bpf-next v3 05/12] selftests/bpf: Allow passing more information to BPF prog test run
- Re: [bpf-next v3 04/12] selftests/bpf: Use bpf_prog_test_run_xattr
- Re: [bpf-next v3 03/12] selftests/bpf: Avoid another case of errno clobbering
- Re: [bpf-next v3 02/12] selftests/bpf: Avoid a clobbering of errno
- Re: [bpf-next v3 01/12] selftests/bpf: Print a message when tester could not run a program
- Re: [bpf-next v3 05/12] selftests/bpf: Allow passing more information to BPF prog test run
- Re: [bpf-next v3 04/12] selftests/bpf: Use bpf_prog_test_run_xattr
- Re: [bpf-next v3 03/12] selftests/bpf: Avoid another case of errno clobbering
- Re: [bpf-next v3 02/12] selftests/bpf: Avoid a clobbering of errno
- Re: [bpf-next v3 01/12] selftests/bpf: Print a message when tester could not run a program
- bpf_prog_free_deferred bug. WAS: Re: WARNING in mark_chain_precision
- Re: WARNING in mark_chain_precision
- Re: WARNING in mark_chain_precision
- Re: WARNING in __mark_chain_precision
- Re: WARNING in mark_chain_precision
- Re: WARNING in __mark_chain_precision
- Re: [PATCH bpf v2] xdp: fix race on generic receive path
- Re: [PATCH v9 net-next 0/5] net: ethernet: ti: cpsw: Add XDP support
- Re: Should we remove xdp-newbies from kernel patch CC-list?
- From: Toke Høiland-Jørgensen
- [PATCH v9 net-next 0/5] net: ethernet: ti: cpsw: Add XDP support
- [PATCH v9 net-next 2/5] net: ethernet: ti: davinci_cpdma: add dma mapped submit
- [PATCH v9 net-next 3/5] net: ethernet: ti: davinci_cpdma: allow desc split while down
- [PATCH v9 net-next 4/5] net: ethernet: ti: cpsw_ethtool: allow res split while down
- [PATCH v9 net-next 5/5] net: ethernet: ti: cpsw: add XDP support
- [PATCH v9 net-next 1/5] net: core: page_pool: add user refcnt and reintroduce page_pool_destroy
- Re: Should we remove xdp-newbies from kernel patch CC-list?
- Re: [PATCH bpf] xdp: fix possible cq entry leak
- Re: [PATCH v8 net-next 0/5] net: ethernet: ti: cpsw: Add XDP support
- possible deadlock in rtnl_lock (6)
- Re: Should we remove xdp-newbies from kernel patch CC-list?
- Re: [bpf-next v3 09/12] bpf: Split out some helper functions
- [bpf-next v3 01/12] selftests/bpf: Print a message when tester could not run a program
- [bpf-next v3 02/12] selftests/bpf: Avoid a clobbering of errno
- [bpf-next v3 03/12] selftests/bpf: Avoid another case of errno clobbering
- [bpf-next v3 04/12] selftests/bpf: Use bpf_prog_test_run_xattr
[Index of Archives]
[Linux Kernel]
[Linux Networking Development]
[Fedora Users]
[Yosemite Campsites]