Skip to contentSkip to conversation

Add support for transmitting packets using XDP in bpf_prog_run()

PATCH Superseded Toke Høiland-Jørgensen 2 participants 20 messages Dec 11, 2021 – Dec 14, 2021

Subsystems (9)

v3 of 11 Superseded Latest is v11 →

lore
Share & tools
lore
#0 lore raw

v3 cover Add support for transmitting packets using XDP in bpf_prog_run()

This series adds support for transmitting packets using XDP in bpf_prog_run(), by enabling the xdp_do_redirect() callback so XDP programs can perform "real" redirects to devices or maps, using an opt-in flag when executing the program.

The primary use case for this is testing the redirect map types and the ndo_xdp_xmit driver operation without generating external traffic. But it turns out to also be useful for creating a programmable traffic generator. The last patch adds a sample traffic generator to bpf/samples, which can transmit up to 11.5 Mpps/core on my test machine.

To transmit the frames, the new mode instantiates a page_pool structure in bpf_prog_run() and initialises the pages with the data passed in by userspace. These pages can then be redirected using the normal redirection mechanism, and the existing page_pool code takes care of returning and recycling them. The setup is optimised for high performance with a high number of repetitions to support stress testing and the traffic generator use case; see patch 6 for details.

The series is structured as follows: Patches 1-2 adds a few features to page_pool that are needed for the usage in bpf_prog_run(). Similarly, patches 3-5 performs a couple of preparatory refactorings of the XDP redirect and memory management code. Patch 6 adds the support to bpf_prog_run() itself, patch 7 adds a selftest, and patch 8 adds the traffic generator example to samples/bpf.

v3:
- Reorder patches to make sure they all build individually (Patchwork)
- Remove a couple of unused variables (Patchwork)
- Remove unlikely() annotation in slow path and add back John's ACK that I accidentally dropped for v2 (John)

v2:
- Split up up __xdp_do_redirect to avoid passing two pointers to it (John)
- Always reset context pointers before each test run (John)
- Use get_mac_addr() from xdp_sample_user.h instead of rolling our own (Kumar)
- Fix wrong offset for metadata pointer

Toke Høiland-Jørgensen (8):
xdp: Allow registering memory model without rxq reference
page_pool: Add callback to init pages when they are allocated
page_pool: Store the XDP mem id
xdp: Move conversion to xdp_frame out of map functions
xdp: add xdp_do_redirect_frame() for pre-computed xdp_frames
bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run() selftests/bpf: Add selftest for XDP_REDIRECT in bpf_prog_run() samples/bpf: Add xdp_trafficgen sample

 include/linux/bpf.h                           |  20 +-
 include/linux/filter.h                        |   4 +
 include/net/page_pool.h                       |  11 +-
 include/net/xdp.h                             |   3 +
 include/uapi/linux/bpf.h                      |   2 +
 kernel/bpf/Kconfig                            |   1 +
 kernel/bpf/cpumap.c                           |   8 +-
 kernel/bpf/devmap.c                           |  32 +-
 net/bpf/test_run.c                            | 217 ++++++++-
 net/core/filter.c                             |  73 ++-
 net/core/page_pool.c                          |   6 +-
 net/core/xdp.c                                |  94 ++--
 samples/bpf/.gitignore                        |   1 +
 samples/bpf/Makefile                          |   4 +
 samples/bpf/xdp_redirect.bpf.c                |  34 ++
 samples/bpf/xdp_trafficgen_user.c             | 421 ++++++++++++++++++
 tools/include/uapi/linux/bpf.h                |   2 +
 .../bpf/prog_tests/xdp_do_redirect.c          |  74 +++
 .../bpf/progs/test_xdp_do_redirect.c          |  34 ++
 19 files changed, 947 insertions(+), 94 deletions(-)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c
 create mode 100644 tools/testing/selftests/bpf/prog_tests/xdp_do_redirect.c
 create mode 100644 tools/testing/selftests/bpf/progs/test_xdp_do_redirect.c
Signature · 1 line
2.34.0
#1 lore raw

PATCH v3 1/8 xdp: Allow registering memory model without rxq reference

The functions that register an XDP memory model take a struct xdp_rxq as parameter, but the RXQ is not actually used for anything other than pulling out the struct xdp_mem_info that it embeds. So refactor the register functions and export variants that just take a pointer to the xdp_mem_info.

This is in preparation for enabling XDP_REDIRECT in bpf_prog_run(), using a page_pool instance that is not connected to any network device.

---
 include/net/xdp.h |  3 ++
 net/core/xdp.c    | 92 +++++++++++++++++++++++++++++++----------------
 2 files changed, 65 insertions(+), 30 deletions(-)
include/net/xdp.h +3 -0
index 447f9b1578f3..8f0812e4996d 100644
@@ -260,6 +260,9 @@ bool xdp_rxq_info_is_reg(struct xdp_rxq_info *xdp_rxq);
 int xdp_rxq_info_reg_mem_model(struct xdp_rxq_info *xdp_rxq,
 			       enum xdp_mem_type type, void *allocator);
 void xdp_rxq_info_unreg_mem_model(struct xdp_rxq_info *xdp_rxq);
+int xdp_reg_mem_model(struct xdp_mem_info *mem,
+		      enum xdp_mem_type type, void *allocator);
+void xdp_unreg_mem_model(struct xdp_mem_info *mem);
 
 /* Drivers not supporting XDP metadata can use this helper, which
  * rejects any room expansion for metadata as a result.
net/core/xdp.c +62 -30

157 lines not on this page · raw message

Signature · 1 line
2.34.0
#2 lore raw

PATCH v3 2/8 page_pool: Add callback to init pages when they are allocated

In reply to Toke Høiland-Jørgensen

Add a new callback function to page_pool that, if set, will be called every time a new page is allocated. This will be used from bpf_test_run() to initialise the page data with the data provided by userspace when running XDP programs with redirect turned on.

---
 include/net/page_pool.h | 2 ++
 net/core/page_pool.c    | 2 ++
 2 files changed, 4 insertions(+)
include/net/page_pool.h +2 -0
index 3855f069627f..a71201854c41 100644
@@ -80,6 +80,8 @@ struct page_pool_params {
 	enum dma_data_direction dma_dir; /* DMA mapping direction */
 	unsigned int	max_len; /* max DMA sync memory size */
 	unsigned int	offset;  /* DMA addr offset */
+	void (*init_callback)(struct page *page, void *arg);
+	void *init_arg;
 };
 
 struct page_pool {
net/core/page_pool.c +2 -0
index 9b60e4301a44..c3b134a86ec9 100644
@@ -219,6 +219,8 @@ static void page_pool_set_pp_info(struct page_pool *pool,
 {
 	page->pp = pool;
 	page->pp_magic |= PP_SIGNATURE;
+	if (pool->p.init_callback)
+		pool->p.init_callback(page, pool->p.init_arg);
 }
 
 static void page_pool_clear_pp_info(struct page *page)
Signature · 1 line
2.34.0
#3 lore raw

PATCH v3 3/8 page_pool: Store the XDP mem id

In reply to Toke Høiland-Jørgensen

Store the XDP mem ID inside the page_pool struct so it can be retrieved later for use in bpf_prog_run().

---
 include/net/page_pool.h | 9 +++++++--
 net/core/page_pool.c    | 4 +++-
 net/core/xdp.c          | 2 +-
 3 files changed, 11 insertions(+), 4 deletions(-)
include/net/page_pool.h +7 -2
index a71201854c41..6bc0409c4ffd 100644
@@ -96,6 +96,7 @@ struct page_pool {
 	unsigned int frag_offset;
 	struct page *frag_page;
 	long frag_users;
+	u32 xdp_mem_id;
 
 	/*
 	 * Data structure for allocation side
@@ -170,9 +171,12 @@ bool page_pool_return_skb_page(struct page *page);
 
 struct page_pool *page_pool_create(const struct page_pool_params *params);
 
+struct xdp_mem_info;
+
 #ifdef CONFIG_PAGE_POOL
 void page_pool_destroy(struct page_pool *pool);
-void page_pool_use_xdp_mem(struct page_pool *pool, void (*disconnect)(void *));
+void page_pool_use_xdp_mem(struct page_pool *pool, void (*disconnect)(void *),
+			   struct xdp_mem_info *mem);
 void page_pool_release_page(struct page_pool *pool, struct page *page);
 void page_pool_put_page_bulk(struct page_pool *pool, void **data,
 			     int count);
@@ -182,7 +186,8 @@ static inline void page_pool_destroy(struct page_pool *pool)
 }
 
 static inline void page_pool_use_xdp_mem(struct page_pool *pool,
-					 void (*disconnect)(void *))
+					 void (*disconnect)(void *),
+					 struct xdp_mem_info *mem)
 {
 }
 static inline void page_pool_release_page(struct page_pool *pool,
net/core/page_pool.c +3 -1
index c3b134a86ec9..8442a7965602 100644
@@ -695,10 +695,12 @@ static void page_pool_release_retry(struct work_struct *wq)
 	schedule_delayed_work(&pool->release_dw, DEFER_TIME);
 }
 
-void page_pool_use_xdp_mem(struct page_pool *pool, void (*disconnect)(void *))
+void page_pool_use_xdp_mem(struct page_pool *pool, void (*disconnect)(void *),
+			   struct xdp_mem_info *mem)
 {
 	refcount_inc(&pool->user_cnt);
 	pool->disconnect = disconnect;
+	pool->xdp_mem_id = mem->id;
 }
 
 void page_pool_destroy(struct page_pool *pool)
net/core/xdp.c +1 -1
index ac476c84a986..2901bb7004cc 100644
@@ -320,7 +320,7 @@ static struct xdp_mem_allocator *__xdp_reg_mem_model(struct xdp_mem_info *mem,
 	}
 
 	if (type == MEM_TYPE_PAGE_POOL)
-		page_pool_use_xdp_mem(allocator, mem_allocator_disconnect);
+		page_pool_use_xdp_mem(allocator, mem_allocator_disconnect, mem);
 
 	mutex_unlock(&mem_id_lock);
 
Signature · 1 line
2.34.0
#4 lore raw

PATCH v3 4/8 xdp: Move conversion to xdp_frame out of map functions

In reply to Toke Høiland-Jørgensen

All map redirect functions except XSK maps convert xdp_buff to xdp_frame before enqueueing it. So move this conversion of out the map functions and into xdp_do_redirect(). This removes a bit of duplicated code, but more importantly it makes it possible to support caller-allocated xdp_frame structures, which will be added in a subsequent commit.

---
 include/linux/bpf.h | 20 ++++++++++----------
 kernel/bpf/cpumap.c |  8 +-------
 kernel/bpf/devmap.c | 32 +++++++++++---------------------
 net/core/filter.c   | 24 +++++++++++++++++-------
 4 files changed, 39 insertions(+), 45 deletions(-)
include/linux/bpf.h +10 -10
index 8bbf08fbab66..691bb397500e 100644
@@ -1621,17 +1621,17 @@ void bpf_patch_call_args(struct bpf_insn *insn, u32 stack_depth);
 struct btf *bpf_get_btf_vmlinux(void);
 
 /* Map specifics */
-struct xdp_buff;
+struct xdp_frame;
 struct sk_buff;
 struct bpf_dtab_netdev;
 struct bpf_cpu_map_entry;
 
 void __dev_flush(void);
-int dev_xdp_enqueue(struct net_device *dev, struct xdp_buff *xdp,
+int dev_xdp_enqueue(struct net_device *dev, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx);
-int dev_map_enqueue(struct bpf_dtab_netdev *dst, struct xdp_buff *xdp,
+int dev_map_enqueue(struct bpf_dtab_netdev *dst, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx);
-int dev_map_enqueue_multi(struct xdp_buff *xdp, struct net_device *dev_rx,
+int dev_map_enqueue_multi(struct xdp_frame *xdpf, struct net_device *dev_rx,
 			  struct bpf_map *map, bool exclude_ingress);
 int dev_map_generic_redirect(struct bpf_dtab_netdev *dst, struct sk_buff *skb,
 			     struct bpf_prog *xdp_prog);
@@ -1640,7 +1640,7 @@ int dev_map_redirect_multi(struct net_device *dev, struct sk_buff *skb,
 			   bool exclude_ingress);
 
 void __cpu_map_flush(void);
-int cpu_map_enqueue(struct bpf_cpu_map_entry *rcpu, struct xdp_buff *xdp,
+int cpu_map_enqueue(struct bpf_cpu_map_entry *rcpu, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx);
 int cpu_map_generic_redirect(struct bpf_cpu_map_entry *rcpu,
 			     struct sk_buff *skb);
@@ -1818,26 +1818,26 @@ static inline void __dev_flush(void)
 {
 }
 
-struct xdp_buff;
+struct xdp_frame;
 struct bpf_dtab_netdev;
 struct bpf_cpu_map_entry;
 
 static inline
-int dev_xdp_enqueue(struct net_device *dev, struct xdp_buff *xdp,
+int dev_xdp_enqueue(struct net_device *dev, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx)
 {
 	return 0;
 }
 
 static inline
-int dev_map_enqueue(struct bpf_dtab_netdev *dst, struct xdp_buff *xdp,
+int dev_map_enqueue(struct bpf_dtab_netdev *dst, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx)
 {
 	return 0;
 }
 
 static inline
-int dev_map_enqueue_multi(struct xdp_buff *xdp, struct net_device *dev_rx,
+int dev_map_enqueue_multi(struct xdp_frame *xdpf, struct net_device *dev_rx,
 			  struct bpf_map *map, bool exclude_ingress)
 {
 	return 0;
@@ -1865,7 +1865,7 @@ static inline void __cpu_map_flush(void)
 }
 
 static inline int cpu_map_enqueue(struct bpf_cpu_map_entry *rcpu,
-				  struct xdp_buff *xdp,
+				  struct xdp_frame *xdpf,
 				  struct net_device *dev_rx)
 {
 	return 0;
kernel/bpf/cpumap.c +1 -7
index 585b2b77ccc4..12798b2c68d9 100644
@@ -746,15 +746,9 @@ static void bq_enqueue(struct bpf_cpu_map_entry *rcpu, struct xdp_frame *xdpf)
 		list_add(&bq->flush_node, flush_list);
 }
 
-int cpu_map_enqueue(struct bpf_cpu_map_entry *rcpu, struct xdp_buff *xdp,
+int cpu_map_enqueue(struct bpf_cpu_map_entry *rcpu, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx)
 {
-	struct xdp_frame *xdpf;
-
-	xdpf = xdp_convert_buff_to_frame(xdp);
-	if (unlikely(!xdpf))
-		return -EOVERFLOW;
-
 	/* Info needed when constructing SKB on remote CPU */
 	xdpf->dev_rx = dev_rx;
 
kernel/bpf/devmap.c +11 -21
index f02d04540c0c..f29f439fac76 100644
@@ -467,24 +467,19 @@ static void bq_enqueue(struct net_device *dev, struct xdp_frame *xdpf,
 	bq->q[bq->count++] = xdpf;
 }
 
-static inline int __xdp_enqueue(struct net_device *dev, struct xdp_buff *xdp,
+static inline int __xdp_enqueue(struct net_device *dev, struct xdp_frame *xdpf,
 				struct net_device *dev_rx,
 				struct bpf_prog *xdp_prog)
 {
-	struct xdp_frame *xdpf;
 	int err;
 
 	if (!dev->netdev_ops->ndo_xdp_xmit)
 		return -EOPNOTSUPP;
 
-	err = xdp_ok_fwd_dev(dev, xdp->data_end - xdp->data);
+	err = xdp_ok_fwd_dev(dev, xdpf->len);
 	if (unlikely(err))
 		return err;
 
-	xdpf = xdp_convert_buff_to_frame(xdp);
-	if (unlikely(!xdpf))
-		return -EOVERFLOW;
-
 	bq_enqueue(dev, xdpf, dev_rx, xdp_prog);
 	return 0;
 }
@@ -520,27 +515,27 @@ static u32 dev_map_bpf_prog_run_skb(struct sk_buff *skb, struct bpf_dtab_netdev
 	return act;
 }
 
-int dev_xdp_enqueue(struct net_device *dev, struct xdp_buff *xdp,
+int dev_xdp_enqueue(struct net_device *dev, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx)
 {
-	return __xdp_enqueue(dev, xdp, dev_rx, NULL);
+	return __xdp_enqueue(dev, xdpf, dev_rx, NULL);
 }
 
-int dev_map_enqueue(struct bpf_dtab_netdev *dst, struct xdp_buff *xdp,
+int dev_map_enqueue(struct bpf_dtab_netdev *dst, struct xdp_frame *xdpf,
 		    struct net_device *dev_rx)
 {
 	struct net_device *dev = dst->dev;
 
-	return __xdp_enqueue(dev, xdp, dev_rx, dst->xdp_prog);
+	return __xdp_enqueue(dev, xdpf, dev_rx, dst->xdp_prog);
 }
 
-static bool is_valid_dst(struct bpf_dtab_netdev *obj, struct xdp_buff *xdp)
+static bool is_valid_dst(struct bpf_dtab_netdev *obj, struct xdp_frame *xdpf)
 {
 	if (!obj ||
 	    !obj->dev->netdev_ops->ndo_xdp_xmit)
 		return false;
 
-	if (xdp_ok_fwd_dev(obj->dev, xdp->data_end - xdp->data))
+	if (xdp_ok_fwd_dev(obj->dev, xdpf->len))
 		return false;
 
 	return true;
@@ -586,14 +581,13 @@ static int get_upper_ifindexes(struct net_device *dev, int *indexes)
 	return n;
 }
 
-int dev_map_enqueue_multi(struct xdp_buff *xdp, struct net_device *dev_rx,
+int dev_map_enqueue_multi(struct xdp_frame *xdpf, struct net_device *dev_rx,
 			  struct bpf_map *map, bool exclude_ingress)
 {
 	struct bpf_dtab *dtab = container_of(map, struct bpf_dtab, map);
 	struct bpf_dtab_netdev *dst, *last_dst = NULL;
 	int excluded_devices[1+MAX_NEST_DEV];
 	struct hlist_head *head;
-	struct xdp_frame *xdpf;
 	int num_excluded = 0;
 	unsigned int i;
 	int err;
@@ -603,15 +597,11 @@ int dev_map_enqueue_multi(struct xdp_buff *xdp, struct net_device *dev_rx,
 		excluded_devices[num_excluded++] = dev_rx->ifindex;
 	}
 
-	xdpf = xdp_convert_buff_to_frame(xdp);
-	if (unlikely(!xdpf))
-		return -EOVERFLOW;
-
 	if (map->map_type == BPF_MAP_TYPE_DEVMAP) {
 		for (i = 0; i < map->max_entries; i++) {
 			dst = rcu_dereference_check(dtab->netdev_map[i],
 						    rcu_read_lock_bh_held());
-			if (!is_valid_dst(dst, xdp))
+			if (!is_valid_dst(dst, xdpf))
 				continue;
 
 			if (is_ifindex_excluded(excluded_devices, num_excluded, dst->dev->ifindex))
@@ -634,7 +624,7 @@ int dev_map_enqueue_multi(struct xdp_buff *xdp, struct net_device *dev_rx,
 			head = dev_map_index_hash(dtab, i);
 			hlist_for_each_entry_rcu(dst, head, index_hlist,
 						 lockdep_is_held(&dtab->index_lock)) {
-				if (!is_valid_dst(dst, xdp))
+				if (!is_valid_dst(dst, xdpf))
 					continue;
 
 				if (is_ifindex_excluded(excluded_devices, num_excluded,
net/core/filter.c +17 -7
index fe27c91e3758..bfa4ffbced35 100644
@@ -3964,12 +3964,24 @@ int xdp_do_redirect(struct net_device *dev, struct xdp_buff *xdp,
 	enum bpf_map_type map_type = ri->map_type;
 	void *fwd = ri->tgt_value;
 	u32 map_id = ri->map_id;
+	struct xdp_frame *xdpf;
 	struct bpf_map *map;
 	int err;
 
 	ri->map_id = 0; /* Valid map id idr range: [1,INT_MAX[ */
 	ri->map_type = BPF_MAP_TYPE_UNSPEC;
 
+	if (map_type == BPF_MAP_TYPE_XSKMAP) {
+		err = __xsk_map_redirect(fwd, xdp);
+		goto out;
+	}
+
+	xdpf = xdp_convert_buff_to_frame(xdp);
+	if (unlikely(!xdpf)) {
+		err = -EOVERFLOW;
+		goto err;
+	}
+
 	switch (map_type) {
 	case BPF_MAP_TYPE_DEVMAP:
 		fallthrough;
@@ -3977,17 +3989,14 @@ int xdp_do_redirect(struct net_device *dev, struct xdp_buff *xdp,
 		map = READ_ONCE(ri->map);
 		if (unlikely(map)) {
 			WRITE_ONCE(ri->map, NULL);
-			err = dev_map_enqueue_multi(xdp, dev, map,
+			err = dev_map_enqueue_multi(xdpf, dev, map,
 						    ri->flags & BPF_F_EXCLUDE_INGRESS);
 		} else {
-			err = dev_map_enqueue(fwd, xdp, dev);
+			err = dev_map_enqueue(fwd, xdpf, dev);
 		}
 		break;
 	case BPF_MAP_TYPE_CPUMAP:
-		err = cpu_map_enqueue(fwd, xdp, dev);
-		break;
-	case BPF_MAP_TYPE_XSKMAP:
-		err = __xsk_map_redirect(fwd, xdp);
+		err = cpu_map_enqueue(fwd, xdpf, dev);
 		break;
 	case BPF_MAP_TYPE_UNSPEC:
 		if (map_id == INT_MAX) {
@@ -3996,7 +4005,7 @@ int xdp_do_redirect(struct net_device *dev, struct xdp_buff *xdp,
 				err = -EINVAL;
 				break;
 			}
-			err = dev_xdp_enqueue(fwd, xdp, dev);
+			err = dev_xdp_enqueue(fwd, xdpf, dev);
 			break;
 		}
 		fallthrough;
@@ -4004,6 +4013,7 @@ int xdp_do_redirect(struct net_device *dev, struct xdp_buff *xdp,
 		err = -EBADRQC;
 	}
 
+out:
 	if (unlikely(err))
 		goto err;
 
Signature · 1 line
2.34.0
#5 lore raw

PATCH v3 5/8 xdp: add xdp_do_redirect_frame() for pre-computed xdp_frames

In reply to Toke Høiland-Jørgensen

Add an xdp_do_redirect_frame() variant which supports pre-computed xdp_frame structures. This will be used in bpf_prog_run() to avoid having to write to the xdp_frame structure when the XDP program doesn't modify the frame boundaries.

---
 include/linux/filter.h |  4 +++
 net/core/filter.c      | 65 +++++++++++++++++++++++++++++++++++-------
 2 files changed, 58 insertions(+), 11 deletions(-)
include/linux/filter.h +4 -0
index b6a216eb217a..845452c83e0f 100644
@@ -1022,6 +1022,10 @@ int xdp_do_generic_redirect(struct net_device *dev, struct sk_buff *skb,
 int xdp_do_redirect(struct net_device *dev,
 		    struct xdp_buff *xdp,
 		    struct bpf_prog *prog);
+int xdp_do_redirect_frame(struct net_device *dev,
+			  struct xdp_buff *xdp,
+			  struct xdp_frame *xdpf,
+			  struct bpf_prog *prog);
 void xdp_do_flush(void);
 
 /* The xdp_do_flush_map() helper has been renamed to drop the _map suffix, as
net/core/filter.c +54 -11

95 lines not on this page · raw message

Signature · 1 line
2.34.0
#6 lore raw

PATCH v3 6/8 bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

In reply to Toke Høiland-Jørgensen

This adds support for doing real redirects when an XDP program returns XDP_REDIRECT in bpf_prog_run(). To achieve this, we create a page pool instance while setting up the test run, and feed pages from that into the XDP program. The setup cost of this is amortised over the number of repetitions specified by userspace.

To support performance testing use case, we further optimise the setup step so that all pages in the pool are pre-initialised with the packet data, and pre-computed context and xdp_frame objects stored at the start of each page. This makes it possible to entirely avoid touching the page content on each XDP program invocation, and enables sending up to 11.5 Mpps/core on my test box.

Because the data pages are recycled by the page pool, and the test runner doesn't re-initialise them for each run, subsequent invocations of the XDP program will see the packet data in the state it was after the last time it ran on that particular page. This means that an XDP program that modifies the packet before redirecting it has to be careful about which assumptions it makes about the packet content, but that is only an issue for the most naively written programs.

Previous uses of bpf_prog_run() for XDP returned the modified packet data and return code to userspace, which is a different semantic then this new redirect mode. For this reason, the caller has to set the new BPF_F_TEST_XDP_DO_REDIRECT flag when calling bpf_prog_run() to opt in to the different semantics. Enabling this flag is only allowed if not setting ctx_out and data_out in the test specification, since it means frames will be redirected somewhere else, so they can't be returned.

---
 include/uapi/linux/bpf.h       |   2 +
 kernel/bpf/Kconfig             |   1 +
 net/bpf/test_run.c             | 217 +++++++++++++++++++++++++++++++--
 tools/include/uapi/linux/bpf.h |   2 +
 4 files changed, 210 insertions(+), 12 deletions(-)
include/uapi/linux/bpf.h +2 -0
index c26871263f1f..224a6e3261f5 100644
@@ -1225,6 +1225,8 @@ enum {
 
 /* If set, run the test on the cpu specified by bpf_attr.test.cpu */
 #define BPF_F_TEST_RUN_ON_CPU	(1U << 0)
+/* If set, support performing redirection of XDP frames */
+#define BPF_F_TEST_XDP_DO_REDIRECT	(1U << 1)
 
 /* type for BPF_ENABLE_STATS */
 enum bpf_stats_type {
kernel/bpf/Kconfig +1 -0
index d24d518ddd63..c8c920020d11 100644
@@ -30,6 +30,7 @@ config BPF_SYSCALL
 	select TASKS_TRACE_RCU
 	select BINARY_PRINTF
 	select NET_SOCK_MSG if NET
+	select PAGE_POOL if NET
 	default n
 	help
 	  Enable the bpf() system call that allows to manipulate BPF programs
net/bpf/test_run.c +205 -12

306 lines not on this page · raw message

tools/include/uapi/linux/bpf.h +2 -0
index c26871263f1f..224a6e3261f5 100644
@@ -1225,6 +1225,8 @@ enum {
 
 /* If set, run the test on the cpu specified by bpf_attr.test.cpu */
 #define BPF_F_TEST_RUN_ON_CPU	(1U << 0)
+/* If set, support performing redirection of XDP frames */
+#define BPF_F_TEST_XDP_DO_REDIRECT	(1U << 1)
 
 /* type for BPF_ENABLE_STATS */
 enum bpf_stats_type {
Signature · 1 line
2.34.0
#7 lore raw

Re: [PATCH bpf-next v3 6/8] bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 201

Quoted 7 lines · Toke Høiland-Jørgensen
net/bpf/test_run.c +7 -0
+
+static void bpf_test_run_xdp_teardown(struct bpf_test_timer *t)
+{
+       struct xdp_mem_info mem = {
+               .id = t->xdp.pp->xdp_mem_id,
+               .type = MEM_TYPE_PAGE_POOL,
+       };

pls add a new line.

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 209

Quoted 8 lines
net/bpf/test_run.c +8 -0
+       xdp_unreg_mem_model(&mem);
+}
+
+static bool ctx_was_changed(struct xdp_page_head *head)
+{
+       return (head->orig_ctx.data != head->ctx.data ||
+               head->orig_ctx.data_meta != head->ctx.data_meta ||
+               head->orig_ctx.data_end != head->ctx.data_end);

redundant ()

net/bpf/test_run.c static int bpf_test_run(struct bpf_prog *prog, void *ctx, u32 repeat, · line 301

Quoted 12 lines
        bpf_test_timer_enter(&t);
        old_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
        do {
                run_ctx.prog_item = &item;
net/bpf/test_run.c +6 -1
-               if (xdp)
+               if (xdp && xdp_redirect) {
+                       ret = bpf_test_run_xdp_redirect(&t, prog, ctx);
+                       if (unlikely(ret < 0))
+                               break;
+                       *retval = ret;
+               } else if (xdp) {
                        *retval = bpf_prog_run_xdp(prog, ctx);

Can we do this unconditionally without introducing a new uapi flag? I mean "return bpf_redirect()" was a nop under test_run. What kind of tests might break if it stops being a nop?

#8 lore raw

Re: [PATCH bpf-next v3 6/8] bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

Quoted 35 lines · Alexei Starovoitov

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 201

Quoted 7 lines · Toke Høiland-Jørgensen
net/bpf/test_run.c +7 -0
+
+static void bpf_test_run_xdp_teardown(struct bpf_test_timer *t)
+{
+       struct xdp_mem_info mem = {
+               .id = t->xdp.pp->xdp_mem_id,
+               .type = MEM_TYPE_PAGE_POOL,
+       };

pls add a new line.

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 209

Quoted 8 lines
net/bpf/test_run.c +8 -0
+       xdp_unreg_mem_model(&mem);
+}
+
+static bool ctx_was_changed(struct xdp_page_head *head)
+{
+       return (head->orig_ctx.data != head->ctx.data ||
+               head->orig_ctx.data_meta != head->ctx.data_meta ||
+               head->orig_ctx.data_end != head->ctx.data_end);

redundant ()

net/bpf/test_run.c static int bpf_test_run(struct bpf_prog *prog, void *ctx, u32 repeat, · line 301

Quoted 12 lines
        bpf_test_timer_enter(&t);
        old_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
        do {
                run_ctx.prog_item = &item;
net/bpf/test_run.c +6 -1
-               if (xdp)
+               if (xdp && xdp_redirect) {
+                       ret = bpf_test_run_xdp_redirect(&t, prog, ctx);
+                       if (unlikely(ret < 0))
+                               break;
+                       *retval = ret;
+               } else if (xdp) {
                        *retval = bpf_prog_run_xdp(prog, ctx);
Quoted 3 lines

Can we do this unconditionally without introducing a new uapi flag? I mean "return bpf_redirect()" was a nop under test_run. What kind of tests might break if it stops being a nop?

Well, I view the existing mode of bpf_prog_test_run() with XDP as a way to write XDP unit tests: it allows you to submit a packet, run your XDP program on it, and check that it returned the right value and did the right modifications. This means if you XDP program does 'return bpf_redirect()', userspace will still get the XDP_REDIRECT value and so it can check correctness of your XDP program.

With this flag the behaviour changes quite drastically, in that it will actually put packets on the wire instead of getting back the program return. So I think it makes more sense to make it a separate opt-in mode; the old behaviour can still be useful for checking XDP program behaviour.

-Toke

#9 lore raw

Re: [PATCH bpf-next v3 6/8] bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

Quoted 49 lines · Toke Høiland-Jørgensen
Quoted 35 lines · Alexei Starovoitov

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 201

Quoted 7 lines · Toke Høiland-Jørgensen
net/bpf/test_run.c +7 -0
+
+static void bpf_test_run_xdp_teardown(struct bpf_test_timer *t)
+{
+       struct xdp_mem_info mem = {
+               .id = t->xdp.pp->xdp_mem_id,
+               .type = MEM_TYPE_PAGE_POOL,
+       };

pls add a new line.

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 209

Quoted 8 lines
net/bpf/test_run.c +8 -0
+       xdp_unreg_mem_model(&mem);
+}
+
+static bool ctx_was_changed(struct xdp_page_head *head)
+{
+       return (head->orig_ctx.data != head->ctx.data ||
+               head->orig_ctx.data_meta != head->ctx.data_meta ||
+               head->orig_ctx.data_end != head->ctx.data_end);

redundant ()

net/bpf/test_run.c static int bpf_test_run(struct bpf_prog *prog, void *ctx, u32 repeat, · line 301

Quoted 12 lines
        bpf_test_timer_enter(&t);
        old_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
        do {
                run_ctx.prog_item = &item;
net/bpf/test_run.c +6 -1
-               if (xdp)
+               if (xdp && xdp_redirect) {
+                       ret = bpf_test_run_xdp_redirect(&t, prog, ctx);
+                       if (unlikely(ret < 0))
+                               break;
+                       *retval = ret;
+               } else if (xdp) {
                        *retval = bpf_prog_run_xdp(prog, ctx);
Quoted 3 lines

Can we do this unconditionally without introducing a new uapi flag? I mean "return bpf_redirect()" was a nop under test_run. What kind of tests might break if it stops being a nop?

Well, I view the existing mode of bpf_prog_test_run() with XDP as a way to write XDP unit tests: it allows you to submit a packet, run your XDP program on it, and check that it returned the right value and did the right modifications. This means if you XDP program does 'return bpf_redirect()', userspace will still get the XDP_REDIRECT value and so it can check correctness of your XDP program.

Quoted 5 lines

With this flag the behaviour changes quite drastically, in that it will actually put packets on the wire instead of getting back the program return. So I think it makes more sense to make it a separate opt-in mode; the old behaviour can still be useful for checking XDP program behaviour.

Ok that all makes sense.
How about using prog_run to feed the data into proper netdev? XDP prog may or may not attach to it (this detail is tbd) and prog_run would use prog_fd and ifindex to trigger RX (yes, receive) in that netdev. XDP prog will execute and will be able to perform all actions (not only XDP_REDIRECT).
XDP_PASS would pass the packet to the stack, etc.

#10 lore raw

Re: [PATCH bpf-next v3 6/8] bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

Quoted 50 lines · Alexei Starovoitov
Quoted 49 lines · Toke Høiland-Jørgensen
Quoted 35 lines · Alexei Starovoitov

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 201

Quoted 7 lines · Toke Høiland-Jørgensen
net/bpf/test_run.c +7 -0
+
+static void bpf_test_run_xdp_teardown(struct bpf_test_timer *t)
+{
+       struct xdp_mem_info mem = {
+               .id = t->xdp.pp->xdp_mem_id,
+               .type = MEM_TYPE_PAGE_POOL,
+       };

pls add a new line.

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 209

Quoted 8 lines
net/bpf/test_run.c +8 -0
+       xdp_unreg_mem_model(&mem);
+}
+
+static bool ctx_was_changed(struct xdp_page_head *head)
+{
+       return (head->orig_ctx.data != head->ctx.data ||
+               head->orig_ctx.data_meta != head->ctx.data_meta ||
+               head->orig_ctx.data_end != head->ctx.data_end);

redundant ()

net/bpf/test_run.c static int bpf_test_run(struct bpf_prog *prog, void *ctx, u32 repeat, · line 301

Quoted 12 lines
        bpf_test_timer_enter(&t);
        old_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
        do {
                run_ctx.prog_item = &item;
net/bpf/test_run.c +6 -1
-               if (xdp)
+               if (xdp && xdp_redirect) {
+                       ret = bpf_test_run_xdp_redirect(&t, prog, ctx);
+                       if (unlikely(ret < 0))
+                               break;
+                       *retval = ret;
+               } else if (xdp) {
                        *retval = bpf_prog_run_xdp(prog, ctx);
Quoted 3 lines

Can we do this unconditionally without introducing a new uapi flag? I mean "return bpf_redirect()" was a nop under test_run. What kind of tests might break if it stops being a nop?

Well, I view the existing mode of bpf_prog_test_run() with XDP as a way to write XDP unit tests: it allows you to submit a packet, run your XDP program on it, and check that it returned the right value and did the right modifications. This means if you XDP program does 'return bpf_redirect()', userspace will still get the XDP_REDIRECT value and so it can check correctness of your XDP program.

Quoted 7 lines
Quoted 5 lines

With this flag the behaviour changes quite drastically, in that it will actually put packets on the wire instead of getting back the program return. So I think it makes more sense to make it a separate opt-in mode; the old behaviour can still be useful for checking XDP program behaviour.

Ok that all makes sense.

Great!

Quoted 6 lines

How about using prog_run to feed the data into proper netdev? XDP prog may or may not attach to it (this detail is tbd) and prog_run would use prog_fd and ifindex to trigger RX (yes, receive) in that netdev. XDP prog will execute and will be able to perform all actions (not only XDP_REDIRECT).
XDP_PASS would pass the packet to the stack, etc.

Hmm, that's certainly an interesting idea! I don't think we can actually run the XDP hook on the netdev itself (since that is deep in the driver), but we can emulate it: we just need to do what this version of the patch is doing, but add handling of the other return codes.

XDP_PASS could be supported by basically copying what cpumap is doing (turn the frames into skbs and call netif_receive_skb_list()), but XDP_TX would have to be implemented via ndo_xdp_xmit(), so it becomes equivalent to a REDIRECT back to the same interface. That's probably OK, though, right?

I'll try this out for the next version, thanks for the idea!

-Toke

#11 lore raw

Re: [PATCH bpf-next v3 6/8] bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

Quoted 75 lines · Toke Høiland-Jørgensen
Quoted 50 lines · Alexei Starovoitov
Quoted 49 lines · Toke Høiland-Jørgensen
Quoted 35 lines · Alexei Starovoitov

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 201

Quoted 7 lines · Toke Høiland-Jørgensen
net/bpf/test_run.c +7 -0
+
+static void bpf_test_run_xdp_teardown(struct bpf_test_timer *t)
+{
+       struct xdp_mem_info mem = {
+               .id = t->xdp.pp->xdp_mem_id,
+               .type = MEM_TYPE_PAGE_POOL,
+       };

pls add a new line.

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 209

Quoted 8 lines
net/bpf/test_run.c +8 -0
+       xdp_unreg_mem_model(&mem);
+}
+
+static bool ctx_was_changed(struct xdp_page_head *head)
+{
+       return (head->orig_ctx.data != head->ctx.data ||
+               head->orig_ctx.data_meta != head->ctx.data_meta ||
+               head->orig_ctx.data_end != head->ctx.data_end);

redundant ()

net/bpf/test_run.c static int bpf_test_run(struct bpf_prog *prog, void *ctx, u32 repeat, · line 301

Quoted 12 lines
        bpf_test_timer_enter(&t);
        old_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
        do {
                run_ctx.prog_item = &item;
net/bpf/test_run.c +6 -1
-               if (xdp)
+               if (xdp && xdp_redirect) {
+                       ret = bpf_test_run_xdp_redirect(&t, prog, ctx);
+                       if (unlikely(ret < 0))
+                               break;
+                       *retval = ret;
+               } else if (xdp) {
                        *retval = bpf_prog_run_xdp(prog, ctx);
Quoted 3 lines

Can we do this unconditionally without introducing a new uapi flag? I mean "return bpf_redirect()" was a nop under test_run. What kind of tests might break if it stops being a nop?

Well, I view the existing mode of bpf_prog_test_run() with XDP as a way to write XDP unit tests: it allows you to submit a packet, run your XDP program on it, and check that it returned the right value and did the right modifications. This means if you XDP program does 'return bpf_redirect()', userspace will still get the XDP_REDIRECT value and so it can check correctness of your XDP program.

Quoted 7 lines
Quoted 5 lines

With this flag the behaviour changes quite drastically, in that it will actually put packets on the wire instead of getting back the program return. So I think it makes more sense to make it a separate opt-in mode; the old behaviour can still be useful for checking XDP program behaviour.

Ok that all makes sense.

Great!

Quoted 6 lines

How about using prog_run to feed the data into proper netdev? XDP prog may or may not attach to it (this detail is tbd) and prog_run would use prog_fd and ifindex to trigger RX (yes, receive) in that netdev. XDP prog will execute and will be able to perform all actions (not only XDP_REDIRECT).
XDP_PASS would pass the packet to the stack, etc.

Hmm, that's certainly an interesting idea! I don't think we can actually run the XDP hook on the netdev itself (since that is deep in the driver), but we can emulate it: we just need to do what this version of the patch is doing, but add handling of the other return codes.

Quoted 5 lines

XDP_PASS could be supported by basically copying what cpumap is doing (turn the frames into skbs and call netif_receive_skb_list()), but XDP_TX would have to be implemented via ndo_xdp_xmit(), so it becomes equivalent to a REDIRECT back to the same interface. That's probably OK, though, right?

Yep. Something like this.
imo the individual BPF_F_TEST_XDP_DO_REDIRECT knob doesn't look right. It's tweaking the prog run from no side effects execution model to partial side effects.
If we want to run xdp prog with side effects it probably should behave like normal execution on the netdev when it receives the packet. We might not even need to create a new netdev for that.
I can imagine a bpf_prog_run operating on eth0 with a packet prepared by the user space.
Like injecting a packet right into the driver and xdp part of it. If prog says XDP_PASS the packet will go up the stack like normal. So this mechanism could be used to inject packets into the stack. Obviously buffer management is an issue in the traditional NIC when a packet doesn't come from the wire.
Also doing this in every driver would be a pain.
So we need some common infra to inject the user packet into a netdev like it was received by this netdev. It could be a change for tuntap or for veth or not related to netdev at all.
After XDP_PASS it doesn't need to be fast. skb will get allocated and the stack might see it as it arrived from ifindex=N regardless of the HW of that netdev.
XDP_TX would xmit right out of that ifindex=netdev.
and XDP_REDIRECT would redirect to a different netdev.
At the end there will be less special cases and page_pool tweaks. Thought the patches 1-5 look fine, it still feels a bit custom just for this particular BPF_F_TEST_XDP_DO_REDIRECT use case. With more generic bpf_run_prog(xdp_prog_fd, ifindex_of_netdev) it might reduce custom handling.

#12 lore raw

Re: [PATCH bpf-next v3 6/8] bpf: Add XDP_REDIRECT support to XDP for bpf_prog_run()

Quoted 92 lines · Alexei Starovoitov
Quoted 75 lines · Toke Høiland-Jørgensen
Quoted 50 lines · Alexei Starovoitov
Quoted 49 lines · Toke Høiland-Jørgensen
Quoted 35 lines · Alexei Starovoitov

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 201

Quoted 7 lines · Toke Høiland-Jørgensen
net/bpf/test_run.c +7 -0
+
+static void bpf_test_run_xdp_teardown(struct bpf_test_timer *t)
+{
+       struct xdp_mem_info mem = {
+               .id = t->xdp.pp->xdp_mem_id,
+               .type = MEM_TYPE_PAGE_POOL,
+       };

pls add a new line.

net/bpf/test_run.c static bool bpf_test_timer_continue(struct bpf_test_timer *t, u32 repeat, int *e · line 209

Quoted 8 lines
net/bpf/test_run.c +8 -0
+       xdp_unreg_mem_model(&mem);
+}
+
+static bool ctx_was_changed(struct xdp_page_head *head)
+{
+       return (head->orig_ctx.data != head->ctx.data ||
+               head->orig_ctx.data_meta != head->ctx.data_meta ||
+               head->orig_ctx.data_end != head->ctx.data_end);

redundant ()

net/bpf/test_run.c static int bpf_test_run(struct bpf_prog *prog, void *ctx, u32 repeat, · line 301

Quoted 12 lines
        bpf_test_timer_enter(&t);
        old_ctx = bpf_set_run_ctx(&run_ctx.run_ctx);
        do {
                run_ctx.prog_item = &item;
net/bpf/test_run.c +6 -1
-               if (xdp)
+               if (xdp && xdp_redirect) {
+                       ret = bpf_test_run_xdp_redirect(&t, prog, ctx);
+                       if (unlikely(ret < 0))
+                               break;
+                       *retval = ret;
+               } else if (xdp) {
                        *retval = bpf_prog_run_xdp(prog, ctx);
Quoted 3 lines

Can we do this unconditionally without introducing a new uapi flag? I mean "return bpf_redirect()" was a nop under test_run. What kind of tests might break if it stops being a nop?

Well, I view the existing mode of bpf_prog_test_run() with XDP as a way to write XDP unit tests: it allows you to submit a packet, run your XDP program on it, and check that it returned the right value and did the right modifications. This means if you XDP program does 'return bpf_redirect()', userspace will still get the XDP_REDIRECT value and so it can check correctness of your XDP program.

Quoted 7 lines
Quoted 5 lines

With this flag the behaviour changes quite drastically, in that it will actually put packets on the wire instead of getting back the program return. So I think it makes more sense to make it a separate opt-in mode; the old behaviour can still be useful for checking XDP program behaviour.

Ok that all makes sense.

Great!

Quoted 6 lines

How about using prog_run to feed the data into proper netdev? XDP prog may or may not attach to it (this detail is tbd) and prog_run would use prog_fd and ifindex to trigger RX (yes, receive) in that netdev. XDP prog will execute and will be able to perform all actions (not only XDP_REDIRECT).
XDP_PASS would pass the packet to the stack, etc.

Hmm, that's certainly an interesting idea! I don't think we can actually run the XDP hook on the netdev itself (since that is deep in the driver), but we can emulate it: we just need to do what this version of the patch is doing, but add handling of the other return codes.

Quoted 5 lines

XDP_PASS could be supported by basically copying what cpumap is doing (turn the frames into skbs and call netif_receive_skb_list()), but XDP_TX would have to be implemented via ndo_xdp_xmit(), so it becomes equivalent to a REDIRECT back to the same interface. That's probably OK, though, right?

Yep. Something like this.
imo the individual BPF_F_TEST_XDP_DO_REDIRECT knob doesn't look right. It's tweaking the prog run from no side effects execution model to partial side effects.
If we want to run xdp prog with side effects it probably should behave like normal execution on the netdev when it receives the packet. We might not even need to create a new netdev for that.
I can imagine a bpf_prog_run operating on eth0 with a packet prepared by the user space.
Like injecting a packet right into the driver and xdp part of it.

Quoted 8 lines

If prog says XDP_PASS the packet will go up the stack like normal. So this mechanism could be used to inject packets into the stack. Obviously buffer management is an issue in the traditional NIC when a packet doesn't come from the wire.
Also doing this in every driver would be a pain.
So we need some common infra to inject the user packet into a netdev like it was received by this netdev. It could be a change for tuntap or for veth or not related to netdev at all.

What you're describing is basically what the cpumap code does; except it doesn't handle XDP_TX, and it doesn't do buffer management. But I already implemented the latter, and the former is straight-forward to do as a special-case XDP_REDIRECT. So my plan is to try this out and see what that looks like :)

Quoted 10 lines

After XDP_PASS it doesn't need to be fast. skb will get allocated and the stack might see it as it arrived from ifindex=N regardless of the HW of that netdev.
XDP_TX would xmit right out of that ifindex=netdev.
and XDP_REDIRECT would redirect to a different netdev. At the end there will be less special cases and page_pool tweaks. Thought the patches 1-5 look fine, it still feels a bit custom just for this particular BPF_F_TEST_XDP_DO_REDIRECT use case. With more generic bpf_run_prog(xdp_prog_fd, ifindex_of_netdev) it might reduce custom handling.

Yup, totally makes sense!

-Toke

#13 lore raw

PATCH v3 7/8 selftests/bpf: Add selftest for XDP_REDIRECT in bpf_prog_run()

In reply to Toke Høiland-Jørgensen

This adds a selftest for the XDP_REDIRECT facility in bpf_prog_run, that redirects packets into a veth and counts them using an XDP program on the other side of the veth pair.

---
 .../bpf/prog_tests/xdp_do_redirect.c          | 74 +++++++++++++++++++
 .../bpf/progs/test_xdp_do_redirect.c          | 34 +++++++++
 2 files changed, 108 insertions(+)
 create mode 100644 tools/testing/selftests/bpf/prog_tests/xdp_do_redirect.c
 create mode 100644 tools/testing/selftests/bpf/progs/test_xdp_do_redirect.c
tools/testing/selftests/bpf/prog_tests/xdp_do_redirect.c new file +74 -0
new file mode 100644
index 000000000000..c2effcf076a6
@@ -0,0 +1,74 @@
+// SPDX-License-Identifier: GPL-2.0
+#include <test_progs.h>
+#include <network_helpers.h>
+#include <net/if.h>
+#include "test_xdp_do_redirect.skel.h"
+
+#define SYS(fmt, ...)						\
+	({							\
+		char cmd[1024];					\
+		snprintf(cmd, sizeof(cmd), fmt, ##__VA_ARGS__);	\
+		if (!ASSERT_OK(system(cmd), cmd))		\
+			goto fail;				\
+	})
+
+#define NUM_PKTS 10
+void test_xdp_do_redirect(void)
+{
+	struct test_xdp_do_redirect *skel = NULL;
+	struct ipv6_packet data = pkt_v6;
+	struct xdp_md ctx_in = { .data_end = sizeof(data) };
+	__u8 dst_mac[ETH_ALEN] = {0x00, 0x11, 0x22, 0x33, 0x44, 0x55};
+	__u8 src_mac[ETH_ALEN] = {0x66, 0x77, 0x88, 0x99, 0xaa, 0xbb};
+	DECLARE_LIBBPF_OPTS(bpf_test_run_opts, opts,
+			    .data_in = &data,
+			    .data_size_in = sizeof(data),
+			    .ctx_in = &ctx_in,
+			    .ctx_size_in = sizeof(ctx_in),
+			    .flags = BPF_F_TEST_XDP_DO_REDIRECT,
+			    .repeat = NUM_PKTS,
+		);
+	int err, prog_fd, ifindex_src, ifindex_dst;
+	struct bpf_link *link;
+
+	memcpy(data.eth.h_dest, dst_mac, ETH_ALEN);
+	memcpy(data.eth.h_source, src_mac, ETH_ALEN);
+
+	skel = test_xdp_do_redirect__open();
+	if (!ASSERT_OK_PTR(skel, "skel"))
+		return;
+
+	SYS("ip link add veth_src type veth peer name veth_dst");
+	SYS("ip link set dev veth_src up");
+	SYS("ip link set dev veth_dst up");
+
+	ifindex_src = if_nametoindex("veth_src");
+	ifindex_dst = if_nametoindex("veth_dst");
+	if (!ASSERT_NEQ(ifindex_src, 0, "ifindex_src") ||
+	    !ASSERT_NEQ(ifindex_dst, 0, "ifindex_dst"))
+		goto fail;
+
+	memcpy(skel->rodata->expect_dst, dst_mac, ETH_ALEN);
+	skel->rodata->ifindex_out = ifindex_src;
+
+	if (!ASSERT_OK(test_xdp_do_redirect__load(skel), "load"))
+		goto fail;
+
+	link = bpf_program__attach_xdp(skel->progs.xdp_count_pkts, ifindex_dst);
+	if (!ASSERT_OK_PTR(link, "prog_attach"))
+		goto fail;
+	skel->links.xdp_count_pkts = link;
+
+	prog_fd = bpf_program__fd(skel->progs.xdp_redirect_notouch);
+	err = bpf_prog_test_run_opts(prog_fd, &opts);
+	if (!ASSERT_OK(err, "prog_run"))
+		goto fail;
+
+	/* wait for the packets to be flushed */
+	kern_sync_rcu();
+
+	ASSERT_EQ(skel->bss->pkts_seen, NUM_PKTS, "pkt_count");
+fail:
+	system("ip link del dev veth_src");
+	test_xdp_do_redirect__destroy(skel);
+}
tools/testing/selftests/bpf/progs/test_xdp_do_redirect.c new file +34 -0
new file mode 100644
index 000000000000..254ebf523f37
@@ -0,0 +1,34 @@
+// SPDX-License-Identifier: GPL-2.0
+#include <vmlinux.h>
+#include <bpf/bpf_helpers.h>
+
+#define ETH_ALEN 6
+const volatile int ifindex_out;
+const volatile __u8 expect_dst[ETH_ALEN];
+volatile int pkts_seen = 0;
+
+SEC("xdp")
+int xdp_redirect_notouch(struct xdp_md *xdp)
+{
+	return bpf_redirect(ifindex_out, 0);
+}
+
+SEC("xdp")
+int xdp_count_pkts(struct xdp_md *xdp)
+{
+	void *data = (void *)(long)xdp->data;
+	void *data_end = (void *)(long)xdp->data_end;
+	struct ethhdr *eth = data;
+	int i;
+
+	if (eth + 1 > data_end)
+		return XDP_ABORTED;
+
+	for (i = 0; i < ETH_ALEN; i++)
+		if (expect_dst[i] != eth->h_dest[i])
+			return XDP_ABORTED;
+	pkts_seen++;
+	return XDP_DROP;
+}
+
+char _license[] SEC("license") = "GPL";
Signature · 1 line
2.34.0
#14 lore raw

PATCH v3 8/8 samples/bpf: Add xdp_trafficgen sample

In reply to Toke Høiland-Jørgensen

This adds an XDP-based traffic generator sample which uses the DO_REDIRECT flag of bpf_prog_run(). It works by building the initial packet in userspace and passing it to the kernel where an XDP program redirects the packet to the target interface. The traffic generator supports two modes of
operation: one that just sends copies of the same packet as fast as it can without touching the packet data at all, and one that rewrites the destination port number of each packet, making the generated traffic span a range of port numbers.

The dynamic mode is included to demonstrate how the bpf_prog_run() facility enables building a completely programmable packet generator using XDP. Using the dynamic mode has about a 10% overhead compared to the static mode, because the latter completely avoids touching the page data.

---
 samples/bpf/.gitignore            |   1 +
 samples/bpf/Makefile              |   4 +
 samples/bpf/xdp_redirect.bpf.c    |  34 +++
 samples/bpf/xdp_trafficgen_user.c | 421 ++++++++++++++++++++++++++++++
 4 files changed, 460 insertions(+)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c
samples/bpf/.gitignore +1 -0
index 0e7bfdbff80a..935672cbdd80 100644
@@ -49,6 +49,7 @@ xdp_redirect_map_multi
 xdp_router_ipv4
 xdp_rxq_info
 xdp_sample_pkts
+xdp_trafficgen
 xdp_tx_iptunnel
 xdpsock
 xdpsock_ctrl_proc
samples/bpf/Makefile +4 -0
index 38638845db9d..d827e0680945 100644
@@ -58,6 +58,7 @@ tprogs-y += xdp_redirect_cpu
 tprogs-y += xdp_redirect_map_multi
 tprogs-y += xdp_redirect_map
 tprogs-y += xdp_redirect
+tprogs-y += xdp_trafficgen
 tprogs-y += xdp_monitor
 
 # Libbpf dependencies
@@ -123,6 +124,7 @@ xdp_redirect_map_multi-objs := xdp_redirect_map_multi_user.o $(XDP_SAMPLE)
 xdp_redirect_cpu-objs := xdp_redirect_cpu_user.o $(XDP_SAMPLE)
 xdp_redirect_map-objs := xdp_redirect_map_user.o $(XDP_SAMPLE)
 xdp_redirect-objs := xdp_redirect_user.o $(XDP_SAMPLE)
+xdp_trafficgen-objs := xdp_trafficgen_user.o $(XDP_SAMPLE)
 xdp_monitor-objs := xdp_monitor_user.o $(XDP_SAMPLE)
 
 # Tell kbuild to always build the programs
@@ -226,6 +228,7 @@ TPROGLDLIBS_map_perf_test	+= -lrt
 TPROGLDLIBS_test_overhead	+= -lrt
 TPROGLDLIBS_xdpsock		+= -pthread -lcap
 TPROGLDLIBS_xsk_fwd		+= -pthread
+TPROGLDLIBS_xdp_trafficgen	+= -pthread
 
 # Allows pointing LLC/CLANG to a LLVM backend with bpf support, redefine on cmdline:
 # make M=samples/bpf LLC=~/git/llvm-project/llvm/build/bin/llc CLANG=~/git/llvm-project/llvm/build/bin/clang
@@ -341,6 +344,7 @@ $(obj)/xdp_redirect_cpu_user.o: $(obj)/xdp_redirect_cpu.skel.h
 $(obj)/xdp_redirect_map_multi_user.o: $(obj)/xdp_redirect_map_multi.skel.h
 $(obj)/xdp_redirect_map_user.o: $(obj)/xdp_redirect_map.skel.h
 $(obj)/xdp_redirect_user.o: $(obj)/xdp_redirect.skel.h
+$(obj)/xdp_trafficgen_user.o: $(obj)/xdp_redirect.skel.h
 $(obj)/xdp_monitor_user.o: $(obj)/xdp_monitor.skel.h
 
 $(obj)/tracex5_kern.o: $(obj)/syscall_nrs.h
samples/bpf/xdp_redirect.bpf.c +34 -0
index 7c02bacfe96b..a09c6f576b79 100644
@@ -39,6 +39,40 @@ int xdp_redirect_prog(struct xdp_md *ctx)
 	return bpf_redirect(ifindex_out, 0);
 }
 
+SEC("xdp")
+int xdp_redirect_notouch(struct xdp_md *ctx)
+{
+	return bpf_redirect(ifindex_out, 0);
+}
+
+const volatile __u16 port_start;
+const volatile __u16 port_range;
+volatile __u16 next_port = 0;
+
+SEC("xdp")
+int xdp_redirect_update_port(struct xdp_md *ctx)
+{
+	void *data_end = (void *)(long)ctx->data_end;
+	void *data = (void *)(long)ctx->data;
+	__u16 cur_port, cksum_diff;
+	struct udphdr *hdr;
+
+	hdr = data + (sizeof(struct ethhdr) + sizeof(struct ipv6hdr));
+	if (hdr + 1 > data_end)
+		return XDP_ABORTED;
+
+	cur_port = bpf_ntohs(hdr->dest);
+	cksum_diff = next_port - cur_port;
+	if (cksum_diff) {
+		hdr->check = bpf_htons(~(~bpf_ntohs(hdr->check) + cksum_diff));
+		hdr->dest = bpf_htons(next_port);
+	}
+	if (next_port++ >= port_start + port_range - 1)
+		next_port = port_start;
+
+	return bpf_redirect(ifindex_out, 0);
+}
+
 /* Redirect require an XDP bpf_prog loaded on the TX device */
 SEC("xdp")
 int xdp_redirect_dummy_prog(struct xdp_md *ctx)
samples/bpf/xdp_trafficgen_user.c new file +421 -0

421 lines not on this page · raw message

Signature · 1 line
2.34.0
#15 lore raw

Re: [PATCH bpf-next v3 8/8] samples/bpf: Add xdp_trafficgen sample

Quoted 15 lines · Toke Høiland-Jørgensen

This adds an XDP-based traffic generator sample which uses the DO_REDIRECT flag of bpf_prog_run(). It works by building the initial packet in userspace and passing it to the kernel where an XDP program redirects the packet to the target interface. The traffic generator supports two modes of
operation: one that just sends copies of the same packet as fast as it can without touching the packet data at all, and one that rewrites the destination port number of each packet, making the generated traffic span a range of port numbers.

The dynamic mode is included to demonstrate how the bpf_prog_run() facility enables building a completely programmable packet generator using XDP. Using the dynamic mode has about a 10% overhead compared to the static mode, because the latter completely avoids touching the page data.

Quoted 8 lines
---
 samples/bpf/.gitignore            |   1 +
 samples/bpf/Makefile              |   4 +
 samples/bpf/xdp_redirect.bpf.c    |  34 +++
 samples/bpf/xdp_trafficgen_user.c | 421 ++++++++++++++++++++++++++++++
 4 files changed, 460 insertions(+)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c

I think it deserves to be in tools/bpf/
samples/bpf/ bit rots too often now.
imo everything in there either needs to be converted to selftests/bpf or deleted.

#16 lore raw

Re: [PATCH bpf-next v3 8/8] samples/bpf: Add xdp_trafficgen sample

Quoted 25 lines · Alexei Starovoitov
Quoted 15 lines · Toke Høiland-Jørgensen

This adds an XDP-based traffic generator sample which uses the DO_REDIRECT flag of bpf_prog_run(). It works by building the initial packet in userspace and passing it to the kernel where an XDP program redirects the packet to the target interface. The traffic generator supports two modes of
operation: one that just sends copies of the same packet as fast as it can without touching the packet data at all, and one that rewrites the destination port number of each packet, making the generated traffic span a range of port numbers.

The dynamic mode is included to demonstrate how the bpf_prog_run() facility enables building a completely programmable packet generator using XDP. Using the dynamic mode has about a 10% overhead compared to the static mode, because the latter completely avoids touching the page data.

Quoted 8 lines
---
 samples/bpf/.gitignore            |   1 +
 samples/bpf/Makefile              |   4 +
 samples/bpf/xdp_redirect.bpf.c    |  34 +++
 samples/bpf/xdp_trafficgen_user.c | 421 ++++++++++++++++++++++++++++++
 4 files changed, 460 insertions(+)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c
Quoted 4 lines

I think it deserves to be in tools/bpf/
samples/bpf/ bit rots too often now.
imo everything in there either needs to be converted to selftests/bpf or deleted.

I think there's value in having a separate set of utilities that are more user-facing than the selftests. But I do agree that it's annoying they bit rot. So how about we fix that instead? Andrii suggested just integrating the build of samples/bpf into selftests[0], so I'll look into that after the holidays. But in the meantime I don't think there's any harm in adding this utility here?

-Toke

[0] https://lore.kernel.org/r/CAEf4BzYv3ONhy-JnQUtknzgBSK0gpm9GBJYtbAiJQe50_eX7Uw@mail.gmail.com

#17 lore raw

Re: [PATCH bpf-next v3 8/8] samples/bpf: Add xdp_trafficgen sample

Quoted 33 lines · Toke Høiland-Jørgensen
Quoted 25 lines · Alexei Starovoitov
Quoted 15 lines · Toke Høiland-Jørgensen

This adds an XDP-based traffic generator sample which uses the DO_REDIRECT flag of bpf_prog_run(). It works by building the initial packet in userspace and passing it to the kernel where an XDP program redirects the packet to the target interface. The traffic generator supports two modes of
operation: one that just sends copies of the same packet as fast as it can without touching the packet data at all, and one that rewrites the destination port number of each packet, making the generated traffic span a range of port numbers.

The dynamic mode is included to demonstrate how the bpf_prog_run() facility enables building a completely programmable packet generator using XDP. Using the dynamic mode has about a 10% overhead compared to the static mode, because the latter completely avoids touching the page data.

Quoted 8 lines
---
 samples/bpf/.gitignore            |   1 +
 samples/bpf/Makefile              |   4 +
 samples/bpf/xdp_redirect.bpf.c    |  34 +++
 samples/bpf/xdp_trafficgen_user.c | 421 ++++++++++++++++++++++++++++++
 4 files changed, 460 insertions(+)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c
Quoted 4 lines

I think it deserves to be in tools/bpf/
samples/bpf/ bit rots too often now.
imo everything in there either needs to be converted to selftests/bpf or deleted.

Quoted 6 lines

I think there's value in having a separate set of utilities that are more user-facing than the selftests. But I do agree that it's annoying they bit rot. So how about we fix that instead? Andrii suggested just integrating the build of samples/bpf into selftests[0], so I'll look into that after the holidays. But in the meantime I don't think there's any harm in adding this utility here?

I think samples/bpf building would help to stabilize bitroting, but the question of the right home for this trafficgen tool remains. I think it's best to keep it outside of the kernel tree. It's not any more special than all other libbpf and bcc tools. I think xdp-tools repo or bcc could be a home for it.

#18 lore raw

Re: [PATCH bpf-next v3 8/8] samples/bpf: Add xdp_trafficgen sample

Quoted 41 lines · Alexei Starovoitov
Quoted 33 lines · Toke Høiland-Jørgensen
Quoted 25 lines · Alexei Starovoitov
Quoted 15 lines · Toke Høiland-Jørgensen

This adds an XDP-based traffic generator sample which uses the DO_REDIRECT flag of bpf_prog_run(). It works by building the initial packet in userspace and passing it to the kernel where an XDP program redirects the packet to the target interface. The traffic generator supports two modes of
operation: one that just sends copies of the same packet as fast as it can without touching the packet data at all, and one that rewrites the destination port number of each packet, making the generated traffic span a range of port numbers.

The dynamic mode is included to demonstrate how the bpf_prog_run() facility enables building a completely programmable packet generator using XDP. Using the dynamic mode has about a 10% overhead compared to the static mode, because the latter completely avoids touching the page data.

Quoted 8 lines
---
 samples/bpf/.gitignore            |   1 +
 samples/bpf/Makefile              |   4 +
 samples/bpf/xdp_redirect.bpf.c    |  34 +++
 samples/bpf/xdp_trafficgen_user.c | 421 ++++++++++++++++++++++++++++++
 4 files changed, 460 insertions(+)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c
Quoted 4 lines

I think it deserves to be in tools/bpf/
samples/bpf/ bit rots too often now.
imo everything in there either needs to be converted to selftests/bpf or deleted.

Quoted 6 lines

I think there's value in having a separate set of utilities that are more user-facing than the selftests. But I do agree that it's annoying they bit rot. So how about we fix that instead? Andrii suggested just integrating the build of samples/bpf into selftests[0], so I'll look into that after the holidays. But in the meantime I don't think there's any harm in adding this utility here?

Quoted 5 lines

I think samples/bpf building would help to stabilize bitroting, but the question of the right home for this trafficgen tool remains. I think it's best to keep it outside of the kernel tree. It's not any more special than all other libbpf and bcc tools. I think xdp-tools repo or bcc could be a home for it.

Alright, I'll drop it from the next version and put it into xdp-tools. I've been contemplating doing the same for some of the other tools (xdp_redirect* and xdp_monitor, for instance). Any opinion on that?

-Toke

#19 lore raw

Re: [PATCH bpf-next v3 8/8] samples/bpf: Add xdp_trafficgen sample

Quoted 50 lines · Toke Høiland-Jørgensen
Quoted 41 lines · Alexei Starovoitov
Quoted 33 lines · Toke Høiland-Jørgensen
Quoted 25 lines · Alexei Starovoitov
Quoted 15 lines · Toke Høiland-Jørgensen

This adds an XDP-based traffic generator sample which uses the DO_REDIRECT flag of bpf_prog_run(). It works by building the initial packet in userspace and passing it to the kernel where an XDP program redirects the packet to the target interface. The traffic generator supports two modes of
operation: one that just sends copies of the same packet as fast as it can without touching the packet data at all, and one that rewrites the destination port number of each packet, making the generated traffic span a range of port numbers.

The dynamic mode is included to demonstrate how the bpf_prog_run() facility enables building a completely programmable packet generator using XDP. Using the dynamic mode has about a 10% overhead compared to the static mode, because the latter completely avoids touching the page data.

Quoted 8 lines
---
 samples/bpf/.gitignore            |   1 +
 samples/bpf/Makefile              |   4 +
 samples/bpf/xdp_redirect.bpf.c    |  34 +++
 samples/bpf/xdp_trafficgen_user.c | 421 ++++++++++++++++++++++++++++++
 4 files changed, 460 insertions(+)
 create mode 100644 samples/bpf/xdp_trafficgen_user.c
Quoted 4 lines

I think it deserves to be in tools/bpf/
samples/bpf/ bit rots too often now.
imo everything in there either needs to be converted to selftests/bpf or deleted.

Quoted 6 lines

I think there's value in having a separate set of utilities that are more user-facing than the selftests. But I do agree that it's annoying they bit rot. So how about we fix that instead? Andrii suggested just integrating the build of samples/bpf into selftests[0], so I'll look into that after the holidays. But in the meantime I don't think there's any harm in adding this utility here?

Quoted 5 lines

I think samples/bpf building would help to stabilize bitroting, but the question of the right home for this trafficgen tool remains. I think it's best to keep it outside of the kernel tree. It's not any more special than all other libbpf and bcc tools. I think xdp-tools repo or bcc could be a home for it.

Quoted 3 lines

Alright, I'll drop it from the next version and put it into xdp-tools. I've been contemplating doing the same for some of the other tools (xdp_redirect* and xdp_monitor, for instance). Any opinion on that?

Please move them too if you don't mind.
samples/ just doesn't have the right production quality vibe. Everything in there is a sample code. In other words a toy application. I hope xdp_trafficgen aims to be a solid maintained tool with a man page that distros will ship eventually.
So starting with a good home is important.