On 09.12.2024 12:21 PM, ValdikSS wrote:
After (presumably) latest UEFI v0033 update for the NUC, my network
is limited to ~250 Mbit/s download unless I disable PCIE ASPM option
in UEFI settings.
56:00.0 Ethernet controller [0200]: Intel Corporation Ethernet
Controller I226-V [8086:125c] (rev 04
gcc-13.2.0
arc allyesconfiggcc-13.2.0
arc axs103_defconfiggcc-13.2.0
arc randconfig-001-20250122gcc-13.2.0
arc randconfig-002-20250122gcc-13.2.0
arm allmodconfig
On 1/22/2025 4:57 PM, ValdikSS wrote:
On 09.12.2024 12:21 PM, ValdikSS wrote:
After (presumably) latest UEFI v0033 update for the NUC, my network
is limited to ~250 Mbit/s download unless I disable PCIE ASPM option
in UEFI settings.
56:00.0 Ethernet controller [0200]: Intel Corporation Ether
On Mon, Jan 20, 2025 at 04:37:55PM +, Simon Horman wrote:
> On Mon, Jan 20, 2025 at 04:50:16PM +0100, Maciej Fijalkowski wrote:
> > Idea behind having ice_rx_buf::act was to simplify and speed up the Rx
> > data path by walking through buffers that were representing cleaned HW
> > Rx descriptor
Introduce a new helper ice_put_rx_mbuf() that will go through gathered
frags from current frame and will call ice_put_rx_buf() on them. Current
logic that was supposed to simplify and optimize the driver where we go
through a batch of all buffers processed in current NAPI instance turned
out to be
v3->v4:
* fix kdoc issues (Simon Horman)
* fix typo in commit msg in patch 1 (Simon Horman)
v2->v3:
* s/intel/iwl in patch subjects (Jakub Kicinski)
v1->v2:
* pass ntc to ice_put_rx_mbuf() (pointed out by Petr Oros) in patch 1
* add review tags from Przemek Kitszel (thanks!)
* make sure patches c
Idea behind having ice_rx_buf::act was to simplify and speed up the Rx
data path by walking through buffers that were representing cleaned HW
Rx descriptors. Since it caused us a major headache recently and we
rolled back to old approach that 'puts' Rx buffers right after running
XDP prog/creating
If we store the pgcnt on few fragments while being in the middle of
gathering the whole frame and we stumbled upon DD bit not being set, we
terminate the NAPI Rx processing loop and come back later on. Then on
next NAPI execution we work on previously stored pgcnt.
Imagine that second half of page
allnoconfiggcc-13.2.0
arc allyesconfiggcc-13.2.0
arcnsimosci_defconfiggcc-13.2.0
arc randconfig-001-20250121gcc-13.2.0
arc randconfig-001-20250122gcc-13.2.0
arc randconfig
gcc-14.2.0
arc allmodconfiggcc-13.2.0
arc allnoconfiggcc-13.2.0
arc allyesconfiggcc-13.2.0
arc defconfiggcc-14.2.0
arc randconfig-001-20250122
Hi Maciej,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tnguy-net-queue/dev-queue]
url:
https://github.com/intel-lab-lkp/linux/commits/Maciej-Fijalkowski/ice-put-Rx-buffers-after-being-done-with-current-frame/20250122-231406
base: https
11 matches
Mail list logo