From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <sdf.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, sdf@fomichev.me,
bobbyeshleman@meta.com, almasrymina@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: devmem: replace gen_pool with freelist
Date: Thu, 3 Sep 2026 19:22:14 -0700 [thread overview]
Message-ID: <20260903192214.3db2fef0@kernel.org> (raw)
In-Reply-To: <20260831183529.2517322-2-sdf@fomichev.me>
On Mon, 31 Aug 2026 11:35:28 -0700 Stanislav Fomichev wrote:
> struct dma_buf *dmabuf;
> - unsigned int sg_idx, i;
> - unsigned long virtual;
> + struct dmabuf_genpool_chunk_owner *owner;
> + unsigned int sg_idx;
reverse xmas tree
The idea makes sense, but indeed hard to merge this without any perf
data to support..
I'll mark this as deferred since it's reaching the top of the queue
for us, please repost when ready.
(BTW for some reason NIPA started showing flakes in qlease around the
time this got into testing branch, but it can't be the reason. Maybe
my split of the GRO test reordered something.)
next prev parent reply other threads:[~2026-09-04 2:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 18:35 [PATCH net-next 0/2] net: devmem: remove gen_pool from dma-buf allocations Stanislav Fomichev
2026-08-31 18:35 ` [PATCH net-next 1/2] net: devmem: replace gen_pool with freelist Stanislav Fomichev
2026-09-04 2:22 ` Jakub Kicinski [this message]
2026-08-31 18:35 ` [PATCH net-next 2/2] net: devmem: embed net_iov_area in binding Stanislav Fomichev
2026-08-31 19:16 ` [PATCH net-next 0/2] net: devmem: remove gen_pool from dma-buf allocations Mina Almasry
2026-09-02 18:36 ` Stanislav Fomichev
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=20260903192214.3db2fef0@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=sdf@fomichev.me \
/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®