Netdev List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Moshe Shemesh <moshe@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Tariq Toukan <tariqt@nvidia.com>
Cc: Eric Dumazet <edumazet@google.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
	Akiva Goldberger <agoldberger@nvidia.com>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
	Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH net-next 0/8] net/mlx5: Prepare eswitch infrastructure for satellite PF support
Date: Thu, 14 May 2026 11:59:25 +0200	[thread overview]
Message-ID: <24313143-d0b2-41af-a95f-62d1f5a16439@redhat.com> (raw)
In-Reply-To: <a0d4052c-2e8d-4dec-afcb-c8050f5d1ac7@redhat.com>

On 5/14/26 11:53 AM, Paolo Abeni wrote:
> On 5/14/26 9:56 AM, Moshe Shemesh wrote:
>> On 5/14/2026 5:25 AM, Jakub Kicinski wrote:
>>> External email: Use caution opening links or attachments
>>>
>>>
>>> On Sun, 10 May 2026 08:34:40 +0300 Tariq Toukan wrote:
>>>> This series prepares the mlx5 eswitch command interface and vport
>>>> infrastructure for satellite PF support.
>>>
>>> Could you perhaps start by explaining what "satellite PF" is?
>>> And how it differs from "socket direct"
>>
>> Satellite PF is another type of Physical Function, its role and 
>> privileges are similar to the host PF, but unlike host PF the Satellite 
>> PF is on the DPU and not on another host. So it's kind of "Satellite" 
>> for the ECPF which is also on the DPU.
>>
>> The next patchset will introduce the Satellite PF, while this patchset 
>> only does some preparations. Small changes to prepare the eswitch to 
>> manage another PF.
>>
>> While Socket Direct is a hardware PCIe topology, that adds another PCIe 
>> link to the NIC, the Satellite PF is just logical entity, by firmware 
>> configuration, no hardware change.
> 
> My understanding is that Jakub wants you to capture the above info in
> the cover letter.

I take my own words back. Actually I'm not sure about the above and
given the constant ML flood I think we prefer to avoid a repost if
possible. The series LGTM, please wait a bit for Jakub eventual explicit
repost request.

Thanks,

Paolo


      reply	other threads:[~2026-05-14  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10  5:34 [PATCH net-next 0/8] net/mlx5: Prepare eswitch infrastructure for satellite PF support Tariq Toukan
2026-05-10  5:34 ` [PATCH net-next 1/8] net/mlx5: Use helper to parse host PF info Tariq Toukan
2026-05-14 19:19   ` Simon Horman
2026-05-10  5:34 ` [PATCH net-next 2/8] net/mlx5: Use v1 response layout for query_esw_functions Tariq Toukan
2026-05-14 19:18   ` Simon Horman
2026-05-10  5:34 ` [PATCH net-next 3/8] net/mlx5: Use mlx5_eswitch_is_vf_vport() for IPsec VF checks Tariq Toukan
2026-05-10  5:34 ` [PATCH net-next 4/8] net/mlx5: Switch vport HCA cap helpers to kvzalloc Tariq Toukan
2026-05-10  5:34 ` [PATCH net-next 5/8] net/mlx5: Add mlx5_vport_set_other_func_general_cap macro Tariq Toukan
2026-05-10  5:34 ` [PATCH net-next 6/8] net/mlx5: Refactor mlx5_set_msix_vec_count() SET_HCA_CAP Tariq Toukan
2026-05-10  5:34 ` [PATCH net-next 7/8] net/mlx5: Use vport helper for IPsec eswitch set caps Tariq Toukan
2026-05-10  5:34 ` [PATCH net-next 8/8] net/mlx5: Generalize enable/disable HCA for any PF vport Tariq Toukan
2026-05-14  2:25 ` [PATCH net-next 0/8] net/mlx5: Prepare eswitch infrastructure for satellite PF support Jakub Kicinski
2026-05-14  7:56   ` Moshe Shemesh
2026-05-14  9:53     ` Paolo Abeni
2026-05-14  9:59       ` Paolo Abeni [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=24313143-d0b2-41af-a95f-62d1f5a16439@redhat.com \
    --to=pabeni@redhat.com \
    --cc=agoldberger@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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