From: Breno Leitao <leitao@debian.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
gustavold@gmail.com, asantostc@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH 0/9] netconsole: stop charging every netpoll user for netconsole-only state
Date: Wed, 27 May 2026 06:22:02 -0700 [thread overview]
Message-ID: <ahbvRJO-P2tgvmXj@gmail.com> (raw)
In-Reply-To: <ahazcZw0KRwu5hUR@gmail.com>
Jakub and netdev maintainers,
On Wed, May 27, 2026 at 10:07:16AM +0100, Breno Leitao wrote:
> On Tue, May 26, 2026 at 07:00:53PM +0000, Jakub Kicinski wrote:
> > On Sun, 24 May 2026 09:12:16 -0700 Breno Leitao wrote:
> > > struct netpoll is shared by every netpoll consumer in the tree:
> > > bonding, bridge, team, vlan, macvlan, dsa and netconsole. The non-
> > > netconsole users only need a per-port handle that lets them transmit
> > > SKBs.
> >
> > Are any of the Sashiko reports real?
>
> Yes, there are real pre-existent issues reported by Sashiko.
>
> > At least one seems legit (parallel device and target removal).
> > If yes we should probably try to fix them before we shuffle the code
> > around?
>
> Ack, I will get them fixed and them move them around.
I was reading Linus' Linux 7.1-rc5 email[1], and I am wondering if these
type of "fixes" should go to net or are you planning to change it to net-next.
"""
These things are "fixes", sure, but at the same time a lot of them
are simply so irrelevant that I think they'd be better off in
a linux-next tree and get merged during the merge window.
""" --linus
Link: https://lore.kernel.org/all/CAHk-=wjt1NiKOdyAMz_DT7NmZ++SizPOhRSi492ukdTnpDzHQw@mail.gmail.com/ [1]
Thanks
--breno
prev parent reply other threads:[~2026-05-27 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 16:12 [PATCH 0/9] netconsole: stop charging every netpoll user for netconsole-only state Breno Leitao
2026-05-24 16:12 ` [PATCH 1/9] netpoll: export refill_skbs(), refill_skbs_work_handler(), skb_pool_flush() Breno Leitao
2026-05-24 16:12 ` [PATCH 2/9] netconsole: take over skb pool lifecycle from netpoll Breno Leitao
2026-05-24 16:12 ` [PATCH 3/9] netconsole: move refill_skbs_work_handler() " Breno Leitao
2026-05-24 16:12 ` [PATCH 4/9] netconsole: move refill_skbs() and skb-pool sizing macros " Breno Leitao
2026-05-24 16:12 ` [PATCH 5/9] netconsole: move skb_pool_flush() " Breno Leitao
2026-05-24 16:12 ` [PATCH 6/9] netconsole: move skb_pool / refill_wq from struct netpoll to netconsole_target Breno Leitao
2026-05-24 16:12 ` [PATCH 7/9] netconsole: move local_port " Breno Leitao
2026-05-24 16:12 ` [PATCH 8/9] netconsole: move remote_port " Breno Leitao
2026-05-24 16:12 ` [PATCH 9/9] netconsole: move remote_mac " Breno Leitao
2026-05-27 2:00 ` [PATCH 0/9] netconsole: stop charging every netpoll user for netconsole-only state Jakub Kicinski
2026-05-27 9:07 ` Breno Leitao
2026-05-27 13:22 ` Breno Leitao [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=ahbvRJO-P2tgvmXj@gmail.com \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavold@gmail.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.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