From: Joe Damato
Date: Mon, 30 Sep 2024 15:17:46 -0700
> On Mon, Sep 30, 2024 at 03:10:41PM +0200, Przemek Kitszel wrote:
>> On 9/30/24 14:38, Alexander Lobakin wrote:
>>> From: Alexander Lobakin
>>> Date: Mon, 30 Sep 2024 14:33:45 +0200
>>>
From: Joe Damato
Date: Wed, 25 Sep 2024 18:
Since the igc driver doesn't support forced speed configuration and
its current related hardware doesn't support it either, there is no
use of the mac.autoneg parameter. Moreover, in one case this usage
might result in a NULL pointer dereference due to an uninitialized
function pointer, phy.ops.for
This is a partial revert to commit 76a0a3f9cc2f ("e1000e: fix force smbus
during suspend flow"). That commit fixed a sporadic PHY access issue but
introduced a regression in runtime suspend flows.
The original issue on Meteor Lake systems was rare in terms of the
reproduction rate and the number of
On 10/1/2024 1:50 PM, Simon Horman wrote:
On Mon, Sep 30, 2024 at 05:12:31PM +, Joe Damato wrote:
Add support for netdev-genl, allowing users to query IRQ, NAPI, and queue
information.
After this patch is applied, note the IRQs assigned to my NIC:
$ cat /proc/interrupts | grep ens | cut
On Tue, Oct 01, 2024 at 03:14:07PM +0200, Alexander Lobakin wrote:
> From: Joe Damato
> Date: Mon, 30 Sep 2024 15:17:46 -0700
>
> > On Mon, Sep 30, 2024 at 03:10:41PM +0200, Przemek Kitszel wrote:
> >> On 9/30/24 14:38, Alexander Lobakin wrote:
> >>> From: Alexander Lobakin
> >>> Date: Mon, 30 S
On Mon, Sep 30, 2024 at 05:12:31PM +, Joe Damato wrote:
> Add support for netdev-genl, allowing users to query IRQ, NAPI, and queue
> information.
>
> After this patch is applied, note the IRQs assigned to my NIC:
>
> $ cat /proc/interrupts | grep ens | cut -f1 --delimiter=':'
> 50
> 51
>
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git 100GbE
branch HEAD: 09d0fb5cb30ebcaed4a33028ae383f5a1463e2b2 idpf: deinit virtchnl
transaction manager after vport and vectors
elapsed time: 829m
configs tested: 94
configs skipped: 3
The following configs have b
On 8/21/2024 4:31 PM, Alexander Lobakin wrote:
From: Wojciech Drewek
Date: Wed, 21 Aug 2024 14:15:32 +0200
From: Jacob Keller
Implement support for reading the PHC time indirectly via the
VIRTCHNL_OP_1588_PTP_GET_TIME operation.
[...]
+/**
+ * iavf_queue_ptp_cmd - Queue PTP command fo
Refactor function ice_get_tx_rx_equa() to iterate over new table of
params instead of multiple calls to ice_aq_get_phy_equalization().
Subsequent commit will extend that function by add more serdes equalizer
values to dump.
Shorten the fields of struct ice_serdes_equalization_to_ethtool for
reada
Extend the work done in commit 70838938e89c ("ice: Implement driver
functionality to dump serdes equalizer values") by adding the new set of
Rx registers that can be read using command:
$ ethtool -d interface_name
Rx equalization parameters are E810 PHY registers used by end user to
gather infor
Extend the work done in commit 70838938e89c ("ice: Implement driver
functionality to dump serdes equalizer values") by refactor the
ice_get_tx_rx_equa() function, shorten struct fields names and add
new Rx registers that can be read using command:
$ ethtool -d interface_name.
Mateusz Polchlopek (
"Arthur Fabre" writes:
> On Mon Sep 30, 2024 at 12:52 PM CEST, Toke Høiland-Jørgensen wrote:
>> > Thinking about it more, my only relectance for a registration API is how
>> > to communicate the ID back to other consumers (our discussion below).
>> >
>> >>
>> >> > Dynamically registering fields m
On Mon, Sep 30, 2024 at 05:12:32PM +, Joe Damato wrote:
> Add support for netdev-genl, allowing users to query IRQ, NAPI, and queue
> information.
>
> After this patch is applied, note the IRQ assigned to my NIC:
>
> $ cat /proc/interrupts | grep enp0s8 | cut -f1 --delimiter=':'
> 18
>
> No
> On Mon Sep 30, 2024 at 1:49 PM CEST, Lorenzo Bianconi wrote:
> > > Lorenzo Bianconi writes:
> > >
> > > >> > We could combine such a registration API with your header format, so
> > > >> > that the registration just becomes a way of allocating one of the
> > > >> > keys
> > > >> > from 0-63 (a
On Mon Sep 30, 2024 at 12:52 PM CEST, Toke Høiland-Jørgensen wrote:
> > Thinking about it more, my only relectance for a registration API is how
> > to communicate the ID back to other consumers (our discussion below).
> >
> >>
> >> > Dynamically registering fields means you have to share the retur
On Mon Sep 30, 2024 at 1:49 PM CEST, Lorenzo Bianconi wrote:
> > Lorenzo Bianconi writes:
> >
> > >> > We could combine such a registration API with your header format, so
> > >> > that the registration just becomes a way of allocating one of the keys
> > >> > from 0-63 (and the registry just bec
From: Mateusz Polchlopek
Date: Tue, 1 Oct 2024 09:20:14 +0200
>
>
> On 8/21/2024 4:31 PM, Alexander Lobakin wrote:
>> From: Wojciech Drewek
>> Date: Wed, 21 Aug 2024 14:15:32 +0200
>>
>>> From: Jacob Keller
>>>
>>> Implement support for reading the PHC time indirectly via the
>>> VIRTCHNL_OP_
On 9/25/24 09:57, Yunsheng Lin wrote:
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.
With all the cach
Lorenzo Bianconi writes:
>> On Mon Sep 30, 2024 at 1:49 PM CEST, Lorenzo Bianconi wrote:
>> > > Lorenzo Bianconi writes:
>> > >
>> > > >> > We could combine such a registration API with your header format, so
>> > > >> > that the registration just becomes a way of allocating one of the
>> > >
Hi Paolo,
Thanks for taking the time.
On Tue, 1 Oct 2024 at 16:32, Paolo Abeni wrote:
>
> On 9/25/24 09:57, Yunsheng Lin wrote:
> > 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 w
On Wed, 2 Oct 2024 at 09:46, Ilias Apalodimas
wrote:
>
> Hi Paolo,
>
> Thanks for taking the time.
>
> On Tue, 1 Oct 2024 at 16:32, Paolo Abeni wrote:
> >
> > On 9/25/24 09:57, Yunsheng Lin wrote:
> > > Networking driver with page_pool support may hand over page
> > > still with dma mapping to ne
Greetings:
Welcome to RFC v4.
Very important and significant changes have been made since RFC v3 [1],
please see the changelog below for details.
A couple important call outs for this revision for reviewers:
1. idpf embeds a napi_struct in an internal data structure and
includes an asser
Allow per-NAPI gro_flush_timeout setting.
The existing sysfs parameter is respected; writes to sysfs will write to
all NAPI structs for the device and the net_device gro_flush_timeout
field. Reads from sysfs will read from the net_device field.
The ability to set gro_flush_timeout on specific NAP
23 matches
Mail list logo
