From: Jakub Kicinski <kuba@kernel.org>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: netdev@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Karol Kolacinski <karol.kolacinski@intel.com>,
intel-wired-lan@lists.osuosl.org,
Jacob Keller <jacob.e.keller@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next 1/3] ice: add ice_adapter for shared data across PFs on the same NIC
Date: Tue, 27 Feb 2024 18:35:55 -0800 [thread overview]
Message-ID: <20240227183555.01123eb7@kernel.org> (raw)
In-Reply-To: <20240226151125.45391-2-mschmidt@redhat.com>
On Mon, 26 Feb 2024 16:11:23 +0100 Michal Schmidt wrote:
> There is a need for synchronization between ice PFs on the same physical
> adapter.
>
> Add a "struct ice_adapter" for holding data shared between PFs of the
> same multifunction PCI device. The struct is refcounted - each ice_pf
> holds a reference to it.
>
> Its first use will be for PTP. I expect it will be useful also to
> improve the ugliness that is ice_prot_id_tbl.
ice doesn't support any multi-host devices?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Richard Cochran <richardcochran@gmail.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Karol Kolacinski <karol.kolacinski@intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] ice: add ice_adapter for shared data across PFs on the same NIC
Date: Tue, 27 Feb 2024 18:35:55 -0800 [thread overview]
Message-ID: <20240227183555.01123eb7@kernel.org> (raw)
In-Reply-To: <20240226151125.45391-2-mschmidt@redhat.com>
On Mon, 26 Feb 2024 16:11:23 +0100 Michal Schmidt wrote:
> There is a need for synchronization between ice PFs on the same physical
> adapter.
>
> Add a "struct ice_adapter" for holding data shared between PFs of the
> same multifunction PCI device. The struct is refcounted - each ice_pf
> holds a reference to it.
>
> Its first use will be for PTP. I expect it will be useful also to
> improve the ugliness that is ice_prot_id_tbl.
ice doesn't support any multi-host devices?
next prev parent reply other threads:[~2024-02-28 2:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 15:11 [Intel-wired-lan] [PATCH net-next 0/3] ice: lighter locking for PTP time reading Michal Schmidt
2024-02-26 15:11 ` Michal Schmidt
2024-02-26 15:11 ` [Intel-wired-lan] [PATCH net-next 1/3] ice: add ice_adapter for shared data across PFs on the same NIC Michal Schmidt
2024-02-26 15:11 ` Michal Schmidt
2024-02-26 19:18 ` [Intel-wired-lan] " Jacob Keller
2024-02-26 19:18 ` Jacob Keller
2024-02-27 7:05 ` [Intel-wired-lan] " Jiri Pirko
2024-02-27 7:05 ` Jiri Pirko
2024-02-27 8:11 ` [Intel-wired-lan] " Michal Schmidt
2024-02-27 8:11 ` Michal Schmidt
2024-02-28 2:35 ` Jakub Kicinski [this message]
2024-02-28 2:35 ` Jakub Kicinski
2024-02-28 17:39 ` [Intel-wired-lan] " Keller, Jacob E
2024-02-28 17:39 ` Keller, Jacob E
2024-02-26 15:11 ` [Intel-wired-lan] [PATCH net-next 2/3] ice: avoid the PTP hardware semaphore in gettimex64 path Michal Schmidt
2024-02-26 15:11 ` Michal Schmidt
2024-02-26 19:36 ` [Intel-wired-lan] " Jacob Keller
2024-02-26 19:36 ` Jacob Keller
2024-02-26 20:11 ` [Intel-wired-lan] " Michal Schmidt
2024-02-26 20:11 ` Michal Schmidt
2024-02-26 21:13 ` [Intel-wired-lan] " Jacob Keller
2024-02-26 21:13 ` Jacob Keller
2024-02-26 15:11 ` [Intel-wired-lan] [PATCH net-next 3/3] ice: fold ice_ptp_read_time into ice_ptp_gettimex64 Michal Schmidt
2024-02-26 15:11 ` Michal Schmidt
2024-02-26 19:36 ` [Intel-wired-lan] " Jacob Keller
2024-02-26 19:36 ` Jacob Keller
2024-02-26 19:16 ` [Intel-wired-lan] [PATCH net-next 0/3] ice: lighter locking for PTP time reading Jacob Keller
2024-02-26 19:16 ` Jacob Keller
2024-02-26 20:01 ` [Intel-wired-lan] " Michal Schmidt
2024-02-26 20:01 ` Michal Schmidt
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=20240227183555.01123eb7@kernel.org \
--to=kuba@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=karol.kolacinski@intel.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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.