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

2025-02-26 Thread Ertman, David M
> -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- > r...@vger.kernel.org; net...@vger.kernel.org; Ertman, David M > > Subject: Re: [iwl-next v4 1/1] iidc/ice/ir

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- > > r...@vger.kernel.org; net...@vge

[Intel-wired-lan] [PATCH] e1000e: Link flap workaround option for false IRP events

2025-02-26 Thread Mark Pearson
Issue is seen on some Lenovo desktop workstations where there is a false IRP event which triggers a link flap. Condition is rare and only seen on networks where link speed may differ along the path between nodes (e.g 10M/100M) Intel are not able to determine root cause but provided a workaround th

[Intel-wired-lan] [tnguy-next-queue:main] BUILD SUCCESS 287044abff8291993ce9565ac6e6a72b85e33b85

2025-02-26 Thread kernel test robot
-14.2.0 arc randconfig-001-20250226gcc-13.2.0 arc randconfig-002-20250226gcc-13.2.0 arm allmodconfigclang-18 arm allmodconfiggcc-14.2.0 arm allnoconfiggcc

Re: [Intel-wired-lan] [RFC net-next v2 1/2] devlink: add whole device devlink instance

2025-02-26 Thread Jiri Pirko
Wed, Feb 26, 2025 at 04:06:19PM +0100, przemyslaw.kits...@intel.com wrote: >On 2/26/25 15:48, Jiri Pirko wrote: >> Tue, Feb 25, 2025 at 04:40:49PM +0100, przemyslaw.kits...@intel.com wrote: >> > On 2/25/25 15:35, Jiri Pirko wrote: >> > > Tue, Feb 25, 2025 at 12:30:49PM +0100, przemyslaw.kits...@int

Re: [Intel-wired-lan] [RFC net-next v2 1/2] devlink: add whole device devlink instance

2025-02-26 Thread Jiri Pirko
Tue, Feb 25, 2025 at 04:40:49PM +0100, przemyslaw.kits...@intel.com wrote: >On 2/25/25 15:35, Jiri Pirko wrote: >> Tue, Feb 25, 2025 at 12:30:49PM +0100, przemyslaw.kits...@intel.com wrote: [...] >> > output, for all PFs and VFs on given device: >> > >> > pci/:af:00: >> > name rss size 8 u

Re: [Intel-wired-lan] [RFC net-next v2 1/2] devlink: add whole device devlink instance

2025-02-26 Thread Przemek Kitszel
On 2/26/25 15:48, Jiri Pirko wrote: Tue, Feb 25, 2025 at 04:40:49PM +0100, przemyslaw.kits...@intel.com wrote: On 2/25/25 15:35, Jiri Pirko wrote: Tue, Feb 25, 2025 at 12:30:49PM +0100, przemyslaw.kits...@intel.com wrote: [...] output, for all PFs and VFs on given device: pci/:af:00:

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

2025-02-26 Thread Ertman, David M
> -Original Message- > From: Leon Romanovsky > Sent: Wednesday, February 26, 2025 10:50 AM > To: Ertman, David M > Cc: Nikolova, Tatyana E ; j...@nvidia.com; > intel-wired-...@lists.osuosl.org; linux-r...@vger.kernel.org; > net...@vger.kernel.org > Subject: Re: [iwl-next v4 1/1] iidc/ic

Re: [Intel-wired-lan] [PATCH] e1000e: Link flap workaround option for false IRP events

2025-02-26 Thread Andrew Lunn
On Wed, Feb 26, 2025 at 02:44:12PM -0500, Mark Pearson wrote: > Issue is seen on some Lenovo desktop workstations where there > is a false IRP event which triggers a link flap. > Condition is rare and only seen on networks where link speed > may differ along the path between nodes (e.g 10M/100M) >

[Intel-wired-lan] [PATCH net-next v10 0/4] fix the DMA API misuse problem for page_pool

2025-02-26 Thread Yunsheng Lin
This patchset fix the dma API misuse problem as below: Networking driver with page_pool support may hand over page still with dma mapping to network stack and try to reuse that page after network stack is done with it and passes it back to page_pool to avoid the penalty of dma mapping/unmapping. Wi

[Intel-wired-lan] [PATCH net-next v10 1/4] page_pool: introduce page_pool_get_pp() API

2025-02-26 Thread Yunsheng Lin
Introduce page_pool_get_pp() API to avoid caller accessing page->pp directly, in order to make the following patch more reviewable as the following patch will change page->pp to page->pp_item to fix the DMA API misuse problem. Signed-off-by: Yunsheng Lin --- drivers/net/ethernet/freescale/fec_ma

[Intel-wired-lan] [PATCH iwl-next v1] ice: refactor the Tx scheduler feature

2025-02-26 Thread Mateusz Polchlopek
Embed ice_get_tx_topo_user_sel() inside the only caller: ice_devlink_tx_sched_layers_get(). Instead of jump from the wrapper to the function that does "get" operation it does "get" itself. Remove unnecessary comment and make usage of str_enabled_disabled() in ice_init_tx_topology(). Suggested-by:

Re: [Intel-wired-lan] [PATCH net-next v9 0/6] net: napi: add CPU affinity to napi->config

2025-02-26 Thread patchwork-bot+netdevbpf
Hello: This series was applied to netdev/net-next.git (main) by Jakub Kicinski : On Mon, 24 Feb 2025 16:22:21 -0700 you wrote: > Drivers usually need to re-apply the user-set IRQ affinity to their IRQs > after reset. However, since there can be only one IRQ affinity notifier > for each IRQ, regis

Re: [Intel-wired-lan] [PATCH net] idpf: fix checksums set in idpf_rx_rsc()

2025-02-26 Thread Przemek Kitszel
On 2/26/25 23:12, Eric Dumazet wrote: idpf_rx_rsc() uses skb_transport_offset(skb) while the transport header is not set yet. This triggers the following warning for CONFIG_DEBUG_NET=y builds. DEBUG_NET_WARN_ON_ONCE(!skb_transport_header_was_set(skb)) [ 69.261620] WARNING: CPU: 7 PID: 0 at .