From: Byungchul Park <byungchul@sk.com>
To: Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel_team@skhynix.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
almasrymina@google.com, hawk@kernel.org, toke@redhat.com,
asml.silence@gmail.com
Subject: Re: [PATCH net-next v3] netmem: replace __netmem_clear_lsb() with netmem_to_nmdesc()
Date: Mon, 29 Sep 2025 16:48:40 +0900 [thread overview]
Message-ID: <20250929074840.GA19203@system.software.com> (raw)
In-Reply-To: <20250929014619.GA20562@system.software.com>
On Mon, Sep 29, 2025 at 10:46:19AM +0900, Byungchul Park wrote:
> On Fri, Sep 26, 2025 at 04:18:45PM +0100, Simon Horman wrote:
> > On Fri, Sep 26, 2025 at 12:54:23PM +0900, Byungchul Park wrote:
> > > Changes from RFC v2:
> > > 1. Add a Reviewed-by tag (Thanks to Mina)
> > > 2. Rebase on main branch as of Sep 22
> > >
> > > Changes from RFC:
> > > 1. Optimize the implementation of netmem_to_nmdesc to use less
> > > instructions (feedbacked by Pavel)
> > >
> > > --->8---
> > > >From 01d23fc4b20c369a2ecf29dc92319d55a4e63aa2 Mon Sep 17 00:00:00 2001
> > > From: Byungchul Park <byungchul@sk.com>
> > > Date: Tue, 29 Jul 2025 19:34:12 +0900
> > > Subject: [PATCH net-next v3] netmem: replace __netmem_clear_lsb() with netmem_to_nmdesc()
> > >
> > > Now that we have struct netmem_desc, it'd better access the pp fields
> > > via struct netmem_desc rather than struct net_iov.
> > >
> > > Introduce netmem_to_nmdesc() for safely converting netmem_ref to
> > > netmem_desc regardless of the type underneath e.i. netmem_desc, net_iov.
> > >
> > > While at it, remove __netmem_clear_lsb() and make netmem_to_nmdesc()
> > > used instead.
> > >
> > > Suggested-by: Pavel Begunkov <asml.silence@gmail.com>
> > > Signed-off-by: Byungchul Park <byungchul@sk.com>
> > > Reviewed-by: Mina Almasry <almasrymina@google.com>
> >
> > Hi Byungchul,
> >
> > Some process issues from my side.
> >
> > 1. The revision information, up to including the '--->8---' line above
> > should be below the scissors ('---') below.
> >
> > This is so that it is available to reviewers, appears in mailing
> > list archives, and so on. But is not included in git history.
>
> Ah yes. Thank you. Lemme check.
>
> > 2. Starting the patch description with a 'From: ' line is fine.
> > But 'Date:" and 'Subject:' lines don't belong there.
> >
> > Perhaps 1 and 2 are some sort of tooling error?
> >
> > 3. Unfortunately while this patch is targeted at net-next,
> > it doesn't apply cleanly there.
>
> I don't understand why. Now I just rebased on the latest 'main' and it
> works well. What should I check else?
I think 1 and 2 ends in 3. I will fix it and resend it after the merge
window.
Byungchul
> > When you repost, be sure to observe the 24h rule.
>
> Thanks!
>
> Byungchul
>
> > Link: https://docs.kernel.org/process/maintainer-netdev.html
> >
> > --
> > pw-bot: changes-requested
> >
> > ...
next prev parent reply other threads:[~2025-09-29 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 3:54 [PATCH net-next v3] netmem: replace __netmem_clear_lsb() with netmem_to_nmdesc() Byungchul Park
2025-09-26 15:18 ` Simon Horman
2025-09-29 1:46 ` Byungchul Park
2025-09-29 7:48 ` Byungchul Park [this message]
2025-09-29 14:11 ` Simon Horman
2025-09-29 17:28 ` Mina Almasry
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=20250929074840.GA19203@system.software.com \
--to=byungchul@sk.com \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=kernel_team@skhynix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@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;
as well as URLs for NNTP newsgroup(s).