mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <harini.katakam@xilinx.com>, <Nicolas.Ferre@microchip.com>,
	<davem@davemloft.net>, <kuba@kernel.org>, <dumazet@google.com>,
	<pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<michal.simek@xilinx.com>, <harinikatakamlinux@gmail.com>,
	<radhey.shyam.pandey@xilinx.com>
Subject: Re: [PATCH] net: macb: Increment rx bd head after allocating skb and buffer
Date: Tue, 10 May 2022 10:11:13 +0000	[thread overview]
Message-ID: <4fb95509-97af-bce5-bf2f-3be8962e5e6a@microchip.com> (raw)
In-Reply-To: <20220509121958.3976-1-harini.katakam@xilinx.com>

On 09.05.2022 15:19, Harini Katakam wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> In gem_rx_refill rx_prepared_head is incremented at the beginning of
> the while loop preparing the skb and data buffers. If the skb or data
> buffer allocation fails, this BD will be unusable BDs until the head
> loops back to the same BD (and obviously buffer allocation succeeds).
> In the unlikely event that there's a string of allocation failures,
> there will be an equal number of unusable BDs and an inconsistent RX
> BD chain. Hence increment the head at the end of the while loop to be
> clean.
> 
> Signed-off-by: Harini Katakam <harini.katakam@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>


> ---
>  drivers/net/ethernet/cadence/macb_main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c
> index 0b03305ad6a0..9c7d590c0188 100644
> --- a/drivers/net/ethernet/cadence/macb_main.c
> +++ b/drivers/net/ethernet/cadence/macb_main.c
> @@ -1215,7 +1215,6 @@ static void gem_rx_refill(struct macb_queue *queue)
>                 /* Make hw descriptor updates visible to CPU */
>                 rmb();
> 
> -               queue->rx_prepared_head++;
>                 desc = macb_rx_desc(queue, entry);
> 
>                 if (!queue->rx_skbuff[entry]) {
> @@ -1254,6 +1253,7 @@ static void gem_rx_refill(struct macb_queue *queue)
>                         dma_wmb();
>                         desc->addr &= ~MACB_BIT(RX_USED);
>                 }
> +               queue->rx_prepared_head++;
>         }
> 
>         /* Make descriptor updates visible to hardware */
> --
> 2.17.1
> 


  reply	other threads:[~2022-05-10 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 12:19 Harini Katakam
2022-05-10 10:11 ` Claudiu.Beznea [this message]
2022-05-10 13:24 ` Paolo Abeni
2022-05-10 13:57   ` Harini Katakam

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=4fb95509-97af-bce5-bf2f-3be8962e5e6a@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=davem@davemloft.net \
    --cc=dumazet@google.com \
    --cc=harini.katakam@xilinx.com \
    --cc=harinikatakamlinux@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@xilinx.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

all inboxes | Powered by JetHome®