mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Thangaraj.S@microchip.com>
To: <gerhard@engleder-embedded.com>
Cc: <andrew+netdev@lunn.ch>, <Bryan.Whitehead@microchip.com>,
	<davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
	<kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>,
	<UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net] net: ethernet: microchip: lan743x: Fix memory allocation failure
Date: Tue, 18 Mar 2025 02:51:44 +0000	[thread overview]
Message-ID: <34d674a3cef104b3b3417645f8b52f0c8972ac08.camel@microchip.com> (raw)
In-Reply-To: <806eed8e-0695-450f-a16b-66b602db01dd@engleder-embedded.com>

Hi Gerhard,
Thanks for reviewing the patch. Please find my response inline.

On Fri, 2025-03-14 at 21:37 +0100, Gerhard Engleder wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On 14.03.25 08:02, Thangaraj Samynathan wrote:
> > The driver allocates ring elements using GFP_ATOMIC and GFP_DMA
> > flags. The allocation is not done in atomic context and there is
> > no dependency from LAN743x hardware on memory allocation should be
> > in DMA_ZONE. Hence modifying the flags to use only GFP_KERNEL.
> > 
> > Signed-off-by: Thangaraj Samynathan <thangaraj.s@microchip.com>
> > ---
> >   drivers/net/ethernet/microchip/lan743x_main.c | 3 +--
> >   1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/drivers/net/ethernet/microchip/lan743x_main.c
> > b/drivers/net/ethernet/microchip/lan743x_main.c
> > index 23760b613d3e..c10b0131d5fb 100644
> > --- a/drivers/net/ethernet/microchip/lan743x_main.c
> > +++ b/drivers/net/ethernet/microchip/lan743x_main.c
> > @@ -2495,8 +2495,7 @@ static int lan743x_rx_process_buffer(struct
> > lan743x_rx *rx)
> > 
> >       /* save existing skb, allocate new skb and map to dma */
> >       skb = buffer_info->skb;
> > -     if (lan743x_rx_init_ring_element(rx, rx->last_head,
> > -                                      GFP_ATOMIC | GFP_DMA)) {
> > +     if (lan743x_rx_init_ring_element(rx, rx->last_head,
> > GFP_KERNEL)) {
> 
> I agree with removing GFP_DMA. If it would be needed, then everywhere
> and not only here in NAPI context as it is intended for hardware
> limitations.
> 
> I'm not sure if GFP_ATOMIC can be removed. Isn't NAPI an atomic
> context?
> For example napi_alloc_skb() and page_pool_dev_alloc_pages() use
> GFP_ATOMIC.
> 

Yes, you are right. GFP ATOMIC cannot be removed. Will address this in
the next revision of the patch

> Gerhard
> 


      reply	other threads:[~2025-03-18  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  7:02 Thangaraj Samynathan
2025-03-14 20:37 ` Gerhard Engleder
2025-03-18  2:51   ` Thangaraj.S [this message]

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=34d674a3cef104b3b3417645f8b52f0c8972ac08.camel@microchip.com \
    --to=thangaraj.s@microchip.com \
    --cc=Bryan.Whitehead@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gerhard@engleder-embedded.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

all inboxes | Powered by JetHome®