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 5/7] net: lan966x: Update dma_dir of page_pool_params
Date: Tue, 22 Nov 2022 12:43:39 +0100 [thread overview]
Message-ID: <20221122114339.419188-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <20221121212850.3212649-6-horatiu.vultur@microchip.com>
From: Horatiu Vultur <horatiu.vultur@microchip.com>
Date: Mon, 21 Nov 2022 22:28:48 +0100
> To add support for XDP_TX it is required to be able to write to the DMA
> area therefore it is required that the pages will be mapped using
> DMA_BIDIRECTIONAL flag.
> Therefore check if there are any xdp programs on the interfaces and in
> that case set DMA_BIDRECTIONAL otherwise use DMA_FROM_DEVICE.
> Therefore when a new XDP program is added it is required to redo the
> page_pool.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> .../ethernet/microchip/lan966x/lan966x_fdma.c | 29 ++++++++++++++----
> .../ethernet/microchip/lan966x/lan966x_main.h | 2 ++
> .../ethernet/microchip/lan966x/lan966x_xdp.c | 30 +++++++++++++++++++
> 3 files changed, 55 insertions(+), 6 deletions(-)
[...]
> diff --git a/drivers/net/ethernet/microchip/lan966x/lan966x_xdp.c b/drivers/net/ethernet/microchip/lan966x/lan966x_xdp.c
> index 8ebde1eb6a09c..05c5a28206558 100644
> --- a/drivers/net/ethernet/microchip/lan966x/lan966x_xdp.c
> +++ b/drivers/net/ethernet/microchip/lan966x/lan966x_xdp.c
> @@ -11,6 +11,8 @@ static int lan966x_xdp_setup(struct net_device *dev, struct netdev_bpf *xdp)
> struct lan966x_port *port = netdev_priv(dev);
> struct lan966x *lan966x = port->lan966x;
> struct bpf_prog *old_prog;
> + bool old_xdp, new_xdp;
> + int err;
>
> if (!lan966x->fdma) {
> NL_SET_ERR_MSG_MOD(xdp->extack,
> @@ -18,7 +20,20 @@ static int lan966x_xdp_setup(struct net_device *dev, struct netdev_bpf *xdp)
> return -EOPNOTSUPP;
> }
>
> + old_xdp = lan966x_xdp_present(lan966x);
> old_prog = xchg(&port->xdp_prog, xdp->prog);
> + new_xdp = lan966x_xdp_present(lan966x);
> +
> + if (old_xdp != new_xdp)
> + goto out;
Shouldn't it be the other way around? E.g. when there's no prog and
you're installing it or there is a prog and we're removing it from
the interface, DMA dir must be changed, so we reload the Pools, but
if `old_xdp == new_xdp` we should just hotswap them and goto out?
> +
> + err = lan966x_fdma_reload_page_pool(lan966x);
> + if (err) {
> + xchg(&port->xdp_prog, old_prog);
> + return err;
> + }
> +
> +out:
> if (old_prog)
> bpf_prog_put(old_prog);
>
[...]
> --
> 2.38.0
Thanks,
Olek
next prev parent reply other threads:[~2022-11-22 11:45 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 [this message]
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
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=20221122114339.419188-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