From: Jakub Kicinski <kuba@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>
Cc: Leon Romanovsky <leon@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
sbhatta@marvell.com, hkelam@marvell.com, sgoutham@marvell.com
Subject: Re: [PATCH net] octeontx2-af: Fix QMEM struct memory allocation
Date: Tue, 3 Jan 2023 19:13:49 -0800 [thread overview]
Message-ID: <20230103191349.30098394@kernel.org> (raw)
In-Reply-To: <Y7P9/7nlpH9TXcld@unreal>
On Tue, 3 Jan 2023 12:05:51 +0200 Leon Romanovsky wrote:
> No, GFP_ATOMIC is for memory allocations in atomic context and not for
> separation between reserved and unreserved memory.
Indeed, using ATOMIC to avoid CMA seems like an odd hack.
I haven't encountered this before.
prev parent reply other threads:[~2023-01-04 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 4:09 [PATCH net] octeontx2-af: Fix QMEM struct memory allocation Geetha sowjanya
2023-01-03 9:00 ` Pavan Chebbi
2023-01-03 10:05 ` Leon Romanovsky
2023-01-04 3:13 ` Jakub Kicinski [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=20230103191349.30098394@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.