From: Frederick Lawler via Intel-wired-lan <intel-wired-lan@osuosl.org>
To: Sergey Temerkhanov <sergey.temerkhanov@intel.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v1 0/3] Rework ctrl_pf pointer usage in struct ice_adapter
Date: Wed, 6 May 2026 12:25:27 -0500 [thread overview]
Message-ID: <aft5h-Ygbjjr4uwk@CMGLRV3> (raw)
In-Reply-To: <20260504110058.2373236-1-sergey.temerkhanov@intel.com>
Hi Sergey,
On Mon, May 04, 2026 at 11:00:55AM +0000, Sergey Temerkhanov wrote:
> Rework usage of the control PF pointer in struct ice_adapter, so that
> it is always has a consistent state, since it is global for an adapter.
> Utilize RCU for reading the pointer value and atomic operations for
> changing it. Zero out the ctrl_pf pointer when the control PF is removed.
>
I'd like to test this series, but I'm having a hard time backporting to
6.18. Is there any prior work I might need to pull in?
Best,
Fred
next prev parent reply other threads:[~2026-05-07 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 11:00 [Intel-wired-lan] [PATCH iwl-net v1 0/3] Rework ctrl_pf pointer usage in struct ice_adapter Sergey Temerkhanov
2026-05-04 11:00 ` [Intel-wired-lan] [PATCH iwl-net v1 1/3] ice: Convert ctrl_pf pointer in struct ice_adapter to RCU Sergey Temerkhanov
2026-05-04 11:00 ` [Intel-wired-lan] [PATCH iwl-net v1 2/3] ice: Zero out the PTP control PF pointer at ice_adapter cleanup Sergey Temerkhanov
2026-05-04 11:00 ` [Intel-wired-lan] [PATCH iwl-net v1 3/3] ice: Cache struct ice_hw pointer for split register reads Sergey Temerkhanov
2026-05-04 11:56 ` [Intel-wired-lan] [PATCH iwl-net v1 0/3] Rework ctrl_pf pointer usage in struct ice_adapter Temerkhanov, Sergey
2026-05-06 17:25 ` Frederick Lawler via Intel-wired-lan [this message]
2026-05-08 11:33 ` Temerkhanov, Sergey
2026-05-08 21:53 ` Frederick Lawler via Intel-wired-lan
2026-05-07 23:22 ` Jacob Keller
2026-05-08 11:19 ` Temerkhanov, Sergey
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=aft5h-Ygbjjr4uwk@CMGLRV3 \
--to=intel-wired-lan@osuosl.org \
--cc=fred@cloudflare.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=sergey.temerkhanov@intel.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.