Netdev List
 help / color / mirror / Atom feed
From: "Björn Töpel" <bjorn@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
	netdev@vger.kernel.org
Cc: bpf@vger.kernel.org, magnus.karlsson@intel.com,
	stfomichev@gmail.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, lorenzo@kernel.org, hawk@kernel.org,
	toke@redhat.com,
	Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Subject: Re: [PATCH RFC net-next 2/4] xdp: return status from generic_xdp_tx()
Date: Tue, 12 May 2026 14:57:38 +0200	[thread overview]
Message-ID: <87bjekkcot.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20260509084858.773921-3-maciej.fijalkowski@intel.com>

Maciej Fijalkowski <maciej.fijalkowski@intel.com> writes:

> Once veth will start to use __do_xdp_generic(), this will be helpful for
> correct stats values being incremented - otherwise we would not have a
> knowledge whether XDP_TX succeeded or not. With this being implemented we
> will only bump xdp_tx stat when actual transmission happened.
>
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> ---
>  include/linux/netdevice.h |  2 +-
>  kernel/bpf/devmap.c       |  2 +-
>  net/core/dev.c            | 11 +++++++++--
>  net/core/filter.c         |  2 +-
>  4 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 47417b2d48a4..473b18b0bb63 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -4255,7 +4255,7 @@ static inline void dev_consume_skb_any(struct sk_buff *skb)
>  
>  u32 bpf_prog_run_generic_xdp(struct sk_buff *skb, struct xdp_buff *xdp,
>  			     const struct bpf_prog *xdp_prog);
> -void generic_xdp_tx(struct sk_buff *skb, const struct bpf_prog *xdp_prog);
> +int generic_xdp_tx(struct sk_buff *skb, const struct bpf_prog *xdp_prog);
>  int do_xdp_generic(const struct bpf_prog *xdp_prog, struct sk_buff **pskb);
>  int netif_rx(struct sk_buff *skb);
>  int __netif_rx(struct sk_buff *skb);
> diff --git a/kernel/bpf/devmap.c b/kernel/bpf/devmap.c
> index 3d619d01088e..b7a4a0266345 100644
> --- a/kernel/bpf/devmap.c
> +++ b/kernel/bpf/devmap.c
> @@ -714,7 +714,7 @@ int dev_map_generic_redirect(struct bpf_dtab_netdev *dst, struct sk_buff *skb,
>  		return 0;
>  
>  	skb->dev = dst->dev;
> -	generic_xdp_tx(skb, xdp_prog);
> +	(void)generic_xdp_tx(skb, xdp_prog);

Why not propagate the error now that we can?

>  
>  	return 0;
>  }
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 6cc2a5bed20f..09012cdea376 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -5628,11 +5628,12 @@ static u32 netif_receive_generic_xdp(struct sk_buff **pskb,
>   * and DDOS attacks will be more effective. In-driver-XDP use dedicated TX
>   * queues, so they do not have this starvation issue.
>   */
> -void generic_xdp_tx(struct sk_buff *skb, const struct bpf_prog *xdp_prog)
> +int generic_xdp_tx(struct sk_buff *skb, const struct bpf_prog *xdp_prog)
>  {
>  	struct net_device *dev = skb->dev;
>  	struct netdev_queue *txq;
>  	bool free_skb = true;
> +	int err = -ENETDOWN;
>  	int cpu, rc;
>  
>  	txq = netdev_core_pick_tx(dev, skb, NULL);
> @@ -5640,8 +5641,12 @@ void generic_xdp_tx(struct sk_buff *skb, const struct bpf_prog *xdp_prog)
>  	HARD_TX_LOCK(dev, txq, cpu);
>  	if (!netif_xmit_frozen_or_drv_stopped(txq)) {
>  		rc = netdev_start_xmit(skb, dev, txq, 0);
> -		if (dev_xmit_complete(rc))
> +		if (dev_xmit_complete(rc)) {
>  			free_skb = false;
> +			err = 0;
> +		} else {
> +			err = -EBUSY;
> +		}
>  	}
>  	HARD_TX_UNLOCK(dev, txq);
>  	if (free_skb) {
> @@ -5649,6 +5654,8 @@ void generic_xdp_tx(struct sk_buff *skb, const struct bpf_prog *xdp_prog)
>  		dev_core_stats_tx_dropped_inc(dev);
>  		kfree_skb(skb);
>  	}
> +
> +	return err;
>  }
>  
>  static DEFINE_STATIC_KEY_FALSE(generic_xdp_needed_key);
> diff --git a/net/core/filter.c b/net/core/filter.c
> index bf9c37b27646..d6d14e0a1e35 100644
> --- a/net/core/filter.c
> +++ b/net/core/filter.c
> @@ -4619,7 +4619,7 @@ int xdp_do_generic_redirect(struct net_device *dev, struct sk_buff *skb,
>  
>  		skb->dev = fwd;
>  		_trace_xdp_redirect(dev, xdp_prog, ri->tgt_index);
> -		generic_xdp_tx(skb, xdp_prog);
> +		(void)generic_xdp_tx(skb, xdp_prog);


Dito.


Björn

  reply	other threads:[~2026-05-12 12:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09  8:48 [PATCH RFC net-next 0/4] xdp: reuse generic skb XDP handling for veth Maciej Fijalkowski
2026-05-09  8:48 ` [PATCH RFC net-next 1/4] xdp: add mixed page_pool/page_shared memory type Maciej Fijalkowski
2026-05-09  8:48 ` [PATCH RFC net-next 2/4] xdp: return status from generic_xdp_tx() Maciej Fijalkowski
2026-05-12 12:57   ` Björn Töpel [this message]
2026-05-12 17:13     ` Maciej Fijalkowski
2026-05-09  8:48 ` [PATCH RFC net-next 3/4] xdp: split generic XDP skb handling Maciej Fijalkowski
2026-05-09  8:48 ` [PATCH RFC net-next 4/4] veth: use generic skb XDP handling Maciej Fijalkowski
2026-05-12 14:32   ` Björn Töpel
2026-05-12 17:06     ` Maciej Fijalkowski
2026-05-12 12:55 ` [PATCH RFC net-next 0/4] xdp: reuse generic skb XDP handling for veth Björn Töpel
2026-05-12 17:12   ` Maciej Fijalkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bjekkcot.fsf@all.your.base.are.belong.to.us \
    --to=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stfomichev@gmail.com \
    --cc=toke@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox