public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v3 7/7] net: lan966x: Add support for XDP_REDIRECT
Date: Tue, 22 Nov 2022 13:04:30 +0100	[thread overview]
Message-ID: <20221122120430.419770-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <20221121212850.3212649-8-horatiu.vultur@microchip.com>

From: Horatiu Vultur <horatiu.vultur@microchip.com>
Date: Mon, 21 Nov 2022 22:28:50 +0100

> Extend lan966x XDP support with the action XDP_REDIRECT. This is similar
> with the XDP_TX, so a lot of functionality can be reused.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>  .../ethernet/microchip/lan966x/lan966x_fdma.c | 83 +++++++++++++++----
>  .../ethernet/microchip/lan966x/lan966x_main.c |  1 +
>  .../ethernet/microchip/lan966x/lan966x_main.h | 10 ++-
>  .../ethernet/microchip/lan966x/lan966x_xdp.c  | 31 ++++++-
>  4 files changed, 109 insertions(+), 16 deletions(-)

[...]

> @@ -558,6 +575,10 @@ static int lan966x_fdma_napi_poll(struct napi_struct *napi, int weight)
>  		case FDMA_TX:
>  			lan966x_fdma_rx_advance_dcb(rx);
>  			continue;
> +		case FDMA_REDIRECT:
> +			lan966x_fdma_rx_advance_dcb(rx);
> +			redirect = true;
> +			continue;

I think you can save a couple lines here and avoid small code dup:

+		case FDMA_REDIRECT:
+			redirect = true;
+			fallthrough;
 		case FDMA_TX:
 			lan966x_fdma_rx_advance_dcb(rx);
 			continue;

The logics stays the same.

>  		case FDMA_DROP:
>  			lan966x_fdma_rx_free_page(rx);
>  			lan966x_fdma_rx_advance_dcb(rx);

[...]

> @@ -178,6 +180,7 @@ struct lan966x_tx_dcb_buf {
>  	struct net_device *dev;
>  	struct sk_buff *skb;
>  	struct xdp_frame *xdpf;
> +	bool xdp_ndo;

I suggest carefully inspecting this struct with pahole (or by just
printkaying its layout/sizes/offsets at runtime) and see if there's
any holes and how it could be optimized.
Also, it's just my personal preference, but it's not that unpopular:
I don't trust bools inside structures as they may surprise with
their sizes or alignment depending on the architercture. Considering
all the blah I wrote, I'd define it as:

struct lan966x_tx_dcb_buf {
	dma_addr_t dma_addr;		// can be 8 bytes on 32-bit plat
	struct net_device *dev;		// ensure natural alignment
	struct sk_buff *skb;
	struct xdp_frame *xdpf;
	u32 len;
	u32 xdp_ndo:1;			// put all your booleans here in
	u32 used:1;			// one u32
	...
};

BTW, we usually do union { skb, xdpf } since they're mutually
exclusive. And to distinguish between XDP and regular Tx you can use
one more bit/bool. This can also come handy later when you add XSk
support (you will be adding it, right? Please :P).

>  	int len;
>  	dma_addr_t dma_addr;
>  	bool used;

[...]

> -- 
> 2.38.0

Thanks,
Olek

  reply	other threads:[~2022-11-22 12:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 21:28 [PATCH net-next v3 0/7] net: lan966x: Extend xdp support Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 1/7] net: lan966x: Add XDP_PACKET_HEADROOM Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 2/7] net: lan966x: Introduce helper functions Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 3/7] net: lan966x: Add len field to lan966x_tx_dcb_buf Horatiu Vultur
2022-11-22 11:30   ` Alexander Lobakin
2022-11-22 21:21     ` Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 4/7] net: lan966x: Update rxq memory model Horatiu Vultur
2022-11-22 11:38   ` Alexander Lobakin
2022-11-22 21:23     ` Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 5/7] net: lan966x: Update dma_dir of page_pool_params Horatiu Vultur
2022-11-22 11:43   ` Alexander Lobakin
2022-11-22 21:25     ` Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 6/7] net: lan966x: Add support for XDP_TX Horatiu Vultur
2022-11-22 16:56   ` Alexander Lobakin
2022-11-22 21:38     ` Horatiu Vultur
2022-11-21 21:28 ` [PATCH net-next v3 7/7] net: lan966x: Add support for XDP_REDIRECT Horatiu Vultur
2022-11-22 12:04   ` Alexander Lobakin [this message]
2022-11-22 21:37     ` Horatiu Vultur
2022-11-23 14:22       ` Alexander Lobakin

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=20221122120430.419770-1-alexandr.lobakin@intel.com \
    --to=alexandr.lobakin@intel.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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