From: Jakub Kicinski <kuba@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: satishkh@cisco.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sebaddel@cisco.com
Subject: Re: [PATCH net-next 1/6] net: add netif_rx_mode_schedule_fresh()
Date: Fri, 25 Sep 2026 18:48:48 -0700 [thread overview]
Message-ID: <20260925184848.770e0aed@kernel.org> (raw)
In-Reply-To: <179029090875.2160803.9750318118693297771@kernel.org>
On Thu, 24 Sep 2026 23:01:48 +0000 netdev-bot+sashiko@kernel.org wrote:
> The kernel-doc says the helper is for callers which need "the complete
> receive configuration to be replayed". Does the helper on its own produce
> that replay for an ndo_set_rx_mode_async driver?
>
> The queued run ends up in netif_rx_mode_run(), which snapshots the address
> lists and then reconciles them. __hw_addr_list_snapshot() copies sync_cnt
> and refcount, __hw_addr_sync_dev() skips entries whose sync_cnt is already
> nonzero, and the reconcile step then computes a zero delta, so addresses
> that were already marked synced are not pushed to the driver again.
I was about to say this, the kdoc promises a full replay which is also
what I suspect you want. but the callback delivers incremental updates
by default so if the device was synced calling this does nothing.
If you do want full replay please fix, and also call it _replay()
we already use that verb eg in udp_tunnel_nic_replay()
If you just want a retry the kdoc and name should be updated..
--
pw-bot: cr
next prev parent reply other threads:[~2026-09-26 1:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 19:59 [PATCH net-next 0/6] enic: configure V2 VF addresses and receive mode Satish Kharat
2026-09-21 19:59 ` [PATCH net-next 1/6] net: add netif_rx_mode_schedule_fresh() Satish Kharat
2026-09-24 23:01 ` netdev-bot+sashiko
2026-09-26 1:48 ` Jakub Kicinski [this message]
2026-09-21 19:59 ` [PATCH net-next 2/6] enic: serialize V2 VF mailbox requests Satish Kharat
2026-09-24 23:01 ` netdev-bot+sashiko
2026-09-21 19:59 ` [PATCH net-next 3/6] enic: recover V2 VF mailbox when PF state is unknown Satish Kharat
2026-09-24 23:01 ` netdev-bot+sashiko
2026-09-21 19:59 ` [PATCH net-next 4/6] enic: validate V2 VF configuration replies Satish Kharat
2026-09-24 23:01 ` netdev-bot+sashiko
2026-09-21 19:59 ` [PATCH net-next 5/6] enic: manage V2 VF station and administrative MAC Satish Kharat
2026-09-24 23:01 ` netdev-bot+sashiko
2026-09-21 19:59 ` [PATCH net-next 6/6] enic: configure V2 VF receive mode over mailbox Satish Kharat
2026-09-24 23:01 ` netdev-bot+sashiko
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=20260925184848.770e0aed@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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®