Re: [Intel-wired-lan] [PATCH iwl-next 05/14] libeth: add control queue support

2025-04-11 Thread Leon Romanovsky
On Thu, Apr 10, 2025 at 03:59:23PM +0200, Larysa Zaremba wrote: > On Thu, Apr 10, 2025 at 04:44:43PM +0300, Leon Romanovsky wrote: > > On Thu, Apr 10, 2025 at 03:05:19PM +0200, Alexander Lobakin wrote: > > > From: Leon Romanovsky > > > Date: Thu, 10 Apr 2025 14:23:49

Re: [Intel-wired-lan] [PATCH iwl-next 05/14] libeth: add control queue support

2025-04-10 Thread Leon Romanovsky
On Thu, Apr 10, 2025 at 02:58:28PM +0200, Larysa Zaremba wrote: > On Thu, Apr 10, 2025 at 02:23:49PM +0300, Leon Romanovsky wrote: > > On Thu, Apr 10, 2025 at 12:44:33PM +0200, Larysa Zaremba wrote: > > > On Thu, Apr 10, 2025 at 11:21:37AM +0300, Leon Romanovsky wrote: > >

Re: [Intel-wired-lan] [PATCH iwl-next 05/14] libeth: add control queue support

2025-04-10 Thread Leon Romanovsky
On Thu, Apr 10, 2025 at 03:33:40PM +0200, Alexander Lobakin wrote: > From: Leon Romanovsky > Date: Thu, 10 Apr 2025 16:27:06 +0300 > > > On Thu, Apr 10, 2025 at 02:58:28PM +0200, Larysa Zaremba wrote: > >> On Thu, Apr 10, 2025 at 02:23:49PM +0300, Leon Romanovsky wro

Re: [Intel-wired-lan] [PATCH iwl-next 05/14] libeth: add control queue support

2025-04-10 Thread Leon Romanovsky
On Thu, Apr 10, 2025 at 03:05:19PM +0200, Alexander Lobakin wrote: > From: Leon Romanovsky > Date: Thu, 10 Apr 2025 14:23:49 +0300 > > > On Thu, Apr 10, 2025 at 12:44:33PM +0200, Larysa Zaremba wrote: > >> On Thu, Apr 10, 2025 at 11:21:37AM +0300, Leon Romanovsky wro

Re: [Intel-wired-lan] [PATCH iwl-next 05/14] libeth: add control queue support

2025-04-10 Thread Leon Romanovsky
On Thu, Apr 10, 2025 at 12:44:33PM +0200, Larysa Zaremba wrote: > On Thu, Apr 10, 2025 at 11:21:37AM +0300, Leon Romanovsky wrote: > > On Tue, Apr 08, 2025 at 02:47:51PM +0200, Larysa Zaremba wrote: > > > From: Phani R Burra > > > > > > Libeth will

Re: [Intel-wired-lan] [PATCH iwl-next 05/14] libeth: add control queue support

2025-04-10 Thread Leon Romanovsky
On Tue, Apr 08, 2025 at 02:47:51PM +0200, Larysa Zaremba wrote: > From: Phani R Burra > > Libeth will now support control queue setup and configuration APIs. > These are mainly used for mailbox communication between drivers and > control plane. > > Make use of the page pool support for managing

Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC to support multiple consumers

2025-03-19 Thread Leon Romanovsky
On Tue, Mar 18, 2025 at 12:45:48PM -0700, Samudrala, Sridhar wrote: > > > On 3/18/2025 10:20 AM, Jason Gunthorpe wrote: > > On Tue, Mar 18, 2025 at 10:01:36AM -0700, Samudrala, Sridhar wrote: > > > > > Yes. Today irdma uses exported symbols from i40e and ice and loading irdma > > > results in bo

Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC to support multiple consumers

2025-03-17 Thread Leon Romanovsky
On Fri, Mar 14, 2025 at 06:18:00PM -0700, Samudrala, Sridhar wrote: > > > On 3/14/2025 11:12 AM, Leon Romanovsky wrote: > > On Thu, Mar 13, 2025 at 04:38:39PM -0700, Samudrala, Sridhar wrote: > > > > > > > > > On 3/2/2025 12:26 AM, Leon Romanovsky wr

Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC to support multiple consumers

2025-03-14 Thread Leon Romanovsky
On Thu, Mar 13, 2025 at 04:38:39PM -0700, Samudrala, Sridhar wrote: > > > On 3/2/2025 12:26 AM, Leon Romanovsky wrote: > > On Wed, Feb 26, 2025 at 11:01:52PM +, Ertman, David M wrote: > > > > > > > > > > -Original Message- > >

Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC to support multiple consumers

2025-03-02 Thread Leon Romanovsky
On Wed, Feb 26, 2025 at 11:01:52PM +, Ertman, David M wrote: > > > > -Original Message- > > From: Leon Romanovsky > > Sent: Wednesday, February 26, 2025 10:50 AM > > To: Ertman, David M > > Cc: Nikolova, Tatyana E ; j...@nvidia.com; > >

Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC to support multiple consumers

2025-02-26 Thread Leon Romanovsky
On Wed, Feb 26, 2025 at 05:36:44PM +, Ertman, David M wrote: > > -Original Message- > > From: Leon Romanovsky > > Sent: Monday, February 24, 2025 11:56 PM > > To: Nikolova, Tatyana E > > Cc: j...@nvidia.com; intel-wired-...@lists.osuosl.org; linux-

Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC to support multiple consumers

2025-02-24 Thread Leon Romanovsky
On Mon, Feb 24, 2025 at 11:04:28PM -0600, Tatyana Nikolova wrote: > From: Dave Ertman > > To support RDMA for E2000 product, the idpf driver will use the IDC > interface with the irdma auxiliary driver, thus becoming a second > consumer of it. This requires the IDC be updated to support multiple

[Intel-wired-lan] [PATCH ipsec-next v1 4/5] xfrm: provide common xdo_dev_offload_ok callback implementation

2025-02-19 Thread Leon Romanovsky
From: Leon Romanovsky Almost all drivers except bond and nsim had same check if device can perform XFRM offload on that specific packet. The check was that packet doesn't have IPv4 options and IPv6 extensions. In NIC drivers, the IPv4 HELEN comparison was slightly different, but the inten

[Intel-wired-lan] [PATCH ipsec-next v1 0/5] Support PMTU in tunnel mode for packet offload

2025-02-19 Thread Leon Romanovsky
their offload can perform encryption for xmit packets. Such common place gives us an option to check MTU and PMTU at one place. Thanks Leon Romanovsky (5): xfrm: delay initialization of offload path till its actually requested xfrm: simplify SA initialization routine xfrm: rely on XFRM of

Re: [Intel-wired-lan] [iwl-next, rdma v3 00/24] Add RDMA support for Intel IPU E2000 (GEN3)

2025-02-16 Thread Leon Romanovsky
On Thu, Feb 13, 2025 at 05:12:46PM +0100, Przemek Kitszel wrote: > On 2/10/25 12:09, Leon Romanovsky wrote: > > On Mon, Feb 10, 2025 at 11:41:31AM +0100, Przemek Kitszel wrote: > > > On 2/7/25 20:49, Tatyana Nikolova wrote: > > > > This patch series is based on 6.1

Re: [Intel-wired-lan] [PATCH ipsec-next 4/5] xfrm: provide common xdo_dev_offload_ok callback implementation

2025-02-16 Thread Leon Romanovsky
On Sun, Feb 16, 2025 at 10:33:59AM +0100, Zhu Yanjun wrote: > 在 2025/2/5 19:20, Leon Romanovsky 写道: > > From: Leon Romanovsky > > > > Almost all drivers except bond and nsim had same check if device > > can perform XFRM offload on that specific packet. The check was t

Re: [Intel-wired-lan] [PATCH ipsec-next 2/5] xfrm: simplify SA initialization routine

2025-02-14 Thread Leon Romanovsky
On Fri, Feb 14, 2025, at 11:29, Steffen Klassert wrote: > On Wed, Feb 12, 2025 at 08:30:20PM +0200, Leon Romanovsky wrote: >> On Wed, Feb 12, 2025 at 12:56:48PM +0100, Steffen Klassert wrote: >> > On Wed, Feb 05, 2025 at 08:20:21PM +0200, Leon Romanovsky wrote: >> &

Re: [Intel-wired-lan] [PATCH ipsec-next 2/5] xfrm: simplify SA initialization routine

2025-02-12 Thread Leon Romanovsky
On Wed, Feb 12, 2025 at 12:56:48PM +0100, Steffen Klassert wrote: > On Wed, Feb 05, 2025 at 08:20:21PM +0200, Leon Romanovsky wrote: > > From: Leon Romanovsky > > > > SA replay mode is initialized differently for user-space and > > kernel-space users, but the call to

Re: [Intel-wired-lan] [iwl-next, rdma v3 00/24] Add RDMA support for Intel IPU E2000 (GEN3)

2025-02-10 Thread Leon Romanovsky
On Mon, Feb 10, 2025 at 11:41:31AM +0100, Przemek Kitszel wrote: > On 2/7/25 20:49, Tatyana Nikolova wrote: > > This patch series is based on 6.14-rc1 and includes both netdev and RDMA > > patches for ease of review. It can also be viewed here [1]. A shared pull > > request will be sent for patches

Re: [Intel-wired-lan] [PATCH ipsec-next 1/5] xfrm: delay initialization of offload path till its actually requested

2025-02-06 Thread Leon Romanovsky
On Thu, Feb 06, 2025 at 07:29:13PM +0530, Bharat Bhushan wrote: > On Thu, Feb 6, 2025 at 2:24 PM Leon Romanovsky wrote: > > > > On Thu, Feb 06, 2025 at 02:16:08PM +0530, Bharat Bhushan wrote: > > > Hi Leon, > > > > > > On Wed, Feb 5, 2025 at 11:50 PM Le

Re: [Intel-wired-lan] [PATCH ipsec-next 1/5] xfrm: delay initialization of offload path till its actually requested

2025-02-06 Thread Leon Romanovsky
On Thu, Feb 06, 2025 at 02:16:08PM +0530, Bharat Bhushan wrote: > Hi Leon, > > On Wed, Feb 5, 2025 at 11:50 PM Leon Romanovsky wrote: > > > > From: Leon Romanovsky > > > > XFRM offload path is probed even if offload isn't needed at all. Let's >

[Intel-wired-lan] [PATCH ipsec-next 0/5] Support PTMU in tunnel mode for packet offload

2025-02-05 Thread Leon Romanovsky
Hi, This series refactors the xdo_dev_offload_ok() to be global place for drivers to check if their offload can perform encryption for xmit packets. Such common place gives us an option to check MTU and PMTU at one place. Thanks Leon Romanovsky (5): xfrm: delay initialization of offload path

[Intel-wired-lan] [PATCH ipsec-next 5/5] xfrm: check for PMTU in tunnel mode for packet offload

2025-02-05 Thread Leon Romanovsky
From: Leon Romanovsky In tunnel mode, for the packet offload, there were no PMTU signaling to the upper level about need to fragment the packet. As a solution, call to already existing xfrm[4|6]_tunnel_check_size() to perform that. Signed-off-by: Leon Romanovsky --- include/net/xfrm.h

[Intel-wired-lan] [PATCH ipsec-next 3/5] xfrm: rely on XFRM offload

2025-02-05 Thread Leon Romanovsky
From: Leon Romanovsky After change of initialization of x->type_offload pointer to be valid only for offloaded SAs. There is no need to rely both on x->type_offload and x->xso.type to determine if SA is offloaded or not. Signed-off-by: Leon Romanovsky --- net/xfrm/xfrm_devi

[Intel-wired-lan] [PATCH ipsec-next 4/5] xfrm: provide common xdo_dev_offload_ok callback implementation

2025-02-05 Thread Leon Romanovsky
From: Leon Romanovsky Almost all drivers except bond and nsim had same check if device can perform XFRM offload on that specific packet. The check was that packet doesn't have IPv4 options and IPv6 extensions. In NIC drivers, the IPv4 HELEN comparison was slightly different, but the inten

[Intel-wired-lan] [PATCH ipsec-next 2/5] xfrm: simplify SA initialization routine

2025-02-05 Thread Leon Romanovsky
From: Leon Romanovsky SA replay mode is initialized differently for user-space and kernel-space users, but the call to xfrm_init_replay() existed in common path with boolean protection. That caused to situation where we have two different function orders. So let's rewrite the SA initializ

[Intel-wired-lan] [PATCH ipsec-next 1/5] xfrm: delay initialization of offload path till its actually requested

2025-02-05 Thread Leon Romanovsky
From: Leon Romanovsky XFRM offload path is probed even if offload isn't needed at all. Let's make sure that x->type_offload pointer stays NULL for such path to reduce ambiguity. Fixes: 9d389d7f84bb ("xfrm: Add a xfrm type offload.") Signed-off-by: Leon Romanovsky

Re: [Intel-wired-lan] [PATCH net v1] ice: do not reserve resources for RDMA when disabled

2024-11-14 Thread Leon Romanovsky
On Wed, Nov 13, 2024 at 04:00:56PM -0800, jbran...@kernel.org wrote: > From: Jesse Brandeburg > > If the CONFIG_INFINIBAND_IRDMA symbol is not enabled as a module or a > built-in, then don't let the driver reserve resources for RDMA. > > Do this by avoiding enabling the capability when scanning