From: Paolo Abeni <pabeni@redhat.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: tatyana.e.nikolova@intel.com, joshua.a.hay@intel.com,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
jgg@ziepe.ca, andrew+netdev@lunn.ch, leon@kernel.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next,rdma-next 0/6][pull request] Add RDMA support for Intel IPU E2000 in idpf
Date: Thu, 17 Jul 2025 12:28:37 +0200 [thread overview]
Message-ID: <245a03a1-a2a0-4975-a68b-c70d22d01d97@redhat.com> (raw)
In-Reply-To: <20250714181002.2865694-1-anthony.l.nguyen@intel.com>
On 7/14/25 8:09 PM, Tony Nguyen wrote:
> This is part two in adding RDMA support for idpf.
> This shared pull request targets both net-next and rdma-next branches
> and is based on tag v6.16-rc1.
>
> IWL reviews:
> v3: https://lore.kernel.org/all/20250708210554.1662-1-tatyana.e.nikolova@intel.com/
> v2: https://lore.kernel.org/all/20250612220002.1120-1-tatyana.e.nikolova@intel.com/
> v1 (split from previous series):
> https://lore.kernel.org/all/20250523170435.668-1-tatyana.e.nikolova@intel.com/
>
> v3: https://lore.kernel.org/all/20250207194931.1569-1-tatyana.e.nikolova@intel.com/
> RFC v2: https://lore.kernel.org/all/20240824031924.421-1-tatyana.e.nikolova@intel.com/
> RFC: https://lore.kernel.org/all/20240724233917.704-1-tatyana.e.nikolova@intel.com/
>
> ----------------------------------------------------------------
> Tatyana Nikolova says:
>
> This idpf patch series is the second part of the staged submission for
> introducing RDMA RoCEv2 support for the IPU E2000 line of products,
> referred to as GEN3.
>
> To support RDMA GEN3 devices, the idpf driver uses common definitions
> of the IIDC interface and implements specific device functionality in
> iidc_rdma_idpf.h.
>
> The IPU model can host one or more logical network endpoints called
> vPorts per PCI function that are flexibly associated with a physical
> port or an internal communication port.
>
> Other features as it pertains to GEN3 devices include:
> * MMIO learning
> * RDMA capability negotiation
> * RDMA vectors discovery between idpf and control plane
>
> These patches are split from the submission "Add RDMA support for Intel
> IPU E2000 (GEN3)" [1]. The patches have been tested on a range of hosts
> and platforms with a variety of general RDMA applications which include
> standalone verbs (rping, perftest, etc.), storage and HPC applications.
>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
>
> [1] https://lore.kernel.org/all/20240724233917.704-1-tatyana.e.nikolova@intel.com/
>
> ----------------------------------------------------------------
I had some conflict while pulling; the automatic resolution looked
correct, but could you please have a look?
Thanks,
Paolo
Thanks
next prev parent reply other threads:[~2025-07-17 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 18:09 [PATCH net-next,rdma-next 0/6][pull request] Add RDMA support for Intel IPU E2000 in idpf Tony Nguyen
2025-07-14 18:09 ` [PATCH net-next,rdma-next 1/6] idpf: use reserved RDMA vectors from control plane Tony Nguyen
2025-07-17 10:30 ` patchwork-bot+netdevbpf
2025-07-14 18:09 ` [PATCH net-next,rdma-next 2/6] idpf: implement core RDMA auxiliary dev create, init, and destroy Tony Nguyen
2025-07-14 18:09 ` [PATCH net-next,rdma-next 3/6] idpf: implement RDMA vport " Tony Nguyen
2025-07-14 18:09 ` [PATCH net-next,rdma-next 4/6] idpf: implement remaining IDC RDMA core callbacks and handlers Tony Nguyen
2025-07-14 18:10 ` [PATCH net-next,rdma-next 5/6] idpf: implement IDC vport aux driver MTU change handler Tony Nguyen
2025-07-14 18:10 ` [PATCH net-next,rdma-next 6/6] idpf: implement get LAN MMIO memory regions Tony Nguyen
2025-07-17 10:28 ` Paolo Abeni [this message]
2025-07-17 16:01 ` [PATCH net-next,rdma-next 0/6][pull request] Add RDMA support for Intel IPU E2000 in idpf Tony Nguyen
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=245a03a1-a2a0-4975-a68b-c70d22d01d97@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tatyana.e.nikolova@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).