From: Lukasz Majewski <lukma@denx.de>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Stefan Wahren <wahrenst@gmx.net>, Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [net-next v11 4/7] net: mtip: The L2 switch driver for imx287
Date: Mon, 19 May 2025 22:52:08 +0200 [thread overview]
Message-ID: <20250519225208.50d60df5@wsk> (raw)
In-Reply-To: <20250516075402.5104a0b6@wsk>
[-- Attachment #1: Type: text/plain, Size: 4575 bytes --]
Hi Paolo,
> Hi Paolo,
>
> > Hi Paolo,
> >
> > > On 5/4/25 4:55 PM, Lukasz Majewski wrote:
> > > > + /* This does 16 byte alignment, exactly what we
> > > > need.
> > > > + * The packet length includes FCS, but we don't
> > > > want to
> > > > + * include that when passing upstream as it
> > > > messes up
> > > > + * bridging applications.
> > > > + */
> > > > + skb = netdev_alloc_skb(pndev, pkt_len +
> > > > NET_IP_ALIGN);
> > > > + if (unlikely(!skb)) {
> > > > + dev_dbg(&fep->pdev->dev,
> > > > + "%s: Memory squeeze, dropping
> > > > packet.\n",
> > > > + pndev->name);
> > > > + pndev->stats.rx_dropped++;
> > > > + goto err_mem;
> > > > + } else {
> > > > + skb_reserve(skb, NET_IP_ALIGN);
> > > > + skb_put(skb, pkt_len); /* Make
> > > > room */
> > > > + skb_copy_to_linear_data(skb, data,
> > > > pkt_len);
> > > > + skb->protocol = eth_type_trans(skb,
> > > > pndev);
> > > > + napi_gro_receive(&fep->napi, skb);
> > > > + }
> > > > +
> > > > + bdp->cbd_bufaddr =
> > > > dma_map_single(&fep->pdev->dev, data,
> > > > +
> > > > bdp->cbd_datlen,
> > > > +
> > > > DMA_FROM_DEVICE);
> > > > + if (unlikely(dma_mapping_error(&fep->pdev->dev,
> > > > +
> > > > bdp->cbd_bufaddr))) {
> > > > + dev_err(&fep->pdev->dev,
> > > > + "Failed to map descriptor rx
> > > > buffer\n");
> > > > + pndev->stats.rx_errors++;
> > > > + pndev->stats.rx_dropped++;
> > > > + dev_kfree_skb_any(skb);
> > > > + goto err_mem;
> > > > + }
> > >
> > > This is doing the mapping and ev. dropping the skb _after_ pushing
> > > the skb up the stack, you must attempt the mapping first.
> >
> > I've double check it - the code seems to be correct.
> >
> > This code is a part of mtip_switch_rx() function, which handles
> > receiving data.
> >
> > First, on probe, the initial dma memory is mapped for MTIP received
> > data.
> >
> > When we receive data, it is processed and afterwards it is "pushed"
> > up to the network stack.
> >
> > As a last step we do map memory for next, incoming data and leave
> > the function.
> >
> > Hence, IMHO, the order is OK and this part shall be left as is.
>
> Is the explanation sufficient?
I would do appreciate your feedback as your OK is required to prepare
v12, so I would had the opportunity to have this patch set accepted to
net-next before cut-off date.
Thanks in advance for your help.
>
> >
> > >
> > > > +static void mtip_free_buffers(struct net_device *dev)
> > > > +{
> > > > + struct mtip_ndev_priv *priv = netdev_priv(dev);
> > > > + struct switch_enet_private *fep = priv->fep;
> > > > + struct sk_buff *skb;
> > > > + struct cbd_t *bdp;
> > > > + int i;
> > > > +
> > > > + bdp = fep->rx_bd_base;
> > > > + for (i = 0; i < RX_RING_SIZE; i++) {
> > > > + skb = fep->rx_skbuff[i];
> > > > +
> > > > + if (bdp->cbd_bufaddr)
> > > > + dma_unmap_single(&fep->pdev->dev,
> > > > bdp->cbd_bufaddr,
> > > > + MTIP_SWITCH_RX_FRSIZE,
> > > > + DMA_FROM_DEVICE);
> > > > + if (skb)
> > > > + dev_kfree_skb(skb);
> > >
> > > I suspect that on error paths mtip_free_buffers() can be invoked
> > > multiple consecutive times with any successful allocation in
> > > between: skb will be freed twice. Likely you need to clear
> > > fep->rx_skbuff[i] here.
> >
> > +1 - I will add it with v12.
> >
> > >
> > > Side note: this patch is way too big for a proper review: you need
> > > to break it in multiple smaller ones, introducing the basic
> > > features separately.
> > >
> > > Cheers,
> > >
> > > Paolo
> > >
> >
> >
> >
> >
> > Best regards,
> >
> > Lukasz Majewski
> >
> > --
> >
> > DENX Software Engineering GmbH, Managing Director: Erika Unter
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
> > Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email:
> > lukma@denx.de
>
>
>
>
> Best regards,
>
> Lukasz Majewski
>
> --
>
> DENX Software Engineering GmbH, Managing Director: Erika Unter
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email:
> lukma@denx.de
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-19 20:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 14:55 [net-next v11 0/7] net: mtip: Add support for MTIP imx287 L2 switch driver Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 1/7] dt-bindings: net: Add MTIP L2 switch description Lukasz Majewski
2025-05-12 16:40 ` Rob Herring
2025-05-13 6:09 ` Lukasz Majewski
2025-05-14 16:01 ` Rob Herring
2025-05-15 8:31 ` Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 2/7] ARM: dts: nxp: mxs: Adjust the imx28.dtsi " Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 3/7] ARM: dts: nxp: mxs: Adjust XEA board's DTS to support L2 switch Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 4/7] net: mtip: The L2 switch driver for imx287 Lukasz Majewski
2025-05-06 10:36 ` Paolo Abeni
2025-05-06 11:04 ` Lukasz Majewski
2025-05-06 11:23 ` Paolo Abeni
2025-05-06 11:29 ` Lukasz Majewski
2025-05-13 5:31 ` Lukasz Majewski
2025-05-16 5:54 ` Lukasz Majewski
2025-05-19 20:52 ` Lukasz Majewski [this message]
2025-05-27 10:35 ` Paolo Abeni
2025-05-27 10:45 ` Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 5/7] ARM: mxs_defconfig: Enable CONFIG_NFS_FSCACHE Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 6/7] ARM: mxs_defconfig: Update mxs_defconfig to 6.15-rc1 Lukasz Majewski
2025-05-04 14:55 ` [net-next v11 7/7] ARM: mxs_defconfig: Enable CONFIG_FEC_MTIP_L2SW to support MTIP L2 switch Lukasz Majewski
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=20250519225208.50d60df5@wsk \
--to=lukma@denx.de \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=horms@kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wahrenst@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).