On Tue, Jun 11, 2024 at 07:38:37PM -0700, Jakub Kicinski wrote:
> On Mon, 10 Jun 2024 17:37:12 +0200 Larysa Zaremba wrote:
> > Fix the problems that are triggered by tx_timeout and ice_xdp() calls,
> > including both pool and program operations.
>
> Is there really no way for ice to fix the lockin
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git 200GbE
branch HEAD: 36534d3c54537bf098224a32dc31397793d4594d tcp: use signed
arithmetic in tcp_rtx_probe0_timed_out()
elapsed time: 1466m
configs tested: 64
configs skipped: 3
The following configs have been buil
On Mon, 10 Jun 2024 17:37:12 +0200 Larysa Zaremba wrote:
> Fix the problems that are triggered by tx_timeout and ice_xdp() calls,
> including both pool and program operations.
Is there really no way for ice to fix the locking? :(
The busy loops and trylocks() are not great, and seem like duct tape
On 6/11/2024 4:47 AM, Alexander Lobakin wrote:
> From: Mateusz Polchlopek
> Date: Tue, 4 Jun 2024 09:13:57 -0400
>
>> From: Jacob Keller
>>
>> Using VIRTCHNL_VF_OFFLOAD_FLEX_DESC, the iAVF driver is capable of
>> negotiating to enable the advanced flexible descriptor layout. Add the
>> flexi
On 6/11/2024 10:21 AM, Maciej Fijalkowski wrote:
On Tue, Jun 11, 2024 at 01:59:37PM +0200, Alexander Lobakin wrote:
ice_clean_xdp_irq_zc(xdp_ring);
+ if (!netif_carrier_ok(xdp_ring->vsi->netdev) ||
+ !netif_running(xdp_ring->vsi->netdev))
+ return true;
On 6/11/2024 12:55 AM, Chien, Richard (Options Engineering) wrote:
>> However, this implementation is wrong. It is exposing the
>> ETHTOOL_GEEPROM and ETHTOOL_SEEPROM interface and abusing it to
>> implement a non-standard interface that is custom to the out-of-tree Intel
>> drivers to support t
On 6/11/2024 3:44 AM, Alexander Lobakin wrote:
From: David Decotigny
Date: Tue, 4 Jun 2024 16:34:48 -0700
On 6/3/2024 11:47 AM, Joshua Hay wrote:
There are several reasons for a TX completion to take longer than usual
to be written back by HW. For example, the completion for a packet th
On Tue, Jun 11, 2024 at 03:01:04PM +0200, Greg Kroah-Hartman wrote:
> In the quest to make struct device constant, start by making
> to_auziliary_drv() return a constant pointer so that drivers that call
> this can be fixed up before the driver core changes.
Acked-by: Mark Brown
signature.asc
D
On Sun, Jun 09, 2024 at 05:33:50PM +, Asbjørn Sloth Tønnesen wrote:
> Now that all drivers properly rejects unsupported flower control flags
> used with FLOW_DISSECTOR_KEY_CONTROL, then time has come to add similar
> checks to the drivers supporting FLOW_DISSECTOR_KEY_ENC_CONTROL.
>
> There ar
> I would also think about why Intel has not submitted this code before?
> Maybe because it does things the wrong way? Please look at how other
> Ethernet drivers support firmware. Is it the same? It might be you need to
> throw away this code and reimplement it to mainline standards, maybe using
>
Hi Greg,
On Tue, Jun 11, 2024 at 03:01:04PM +0200, Greg Kroah-Hartman wrote:
> In the quest to make struct device constant, start by making
> to_auziliary_drv() return a constant pointer so that drivers that call
s/z/s/
Acked-by: Sakari Ailus #
drivers/media/pci/intel/ipu6
> this can be fixed
> However, this implementation is wrong. It is exposing the
> ETHTOOL_GEEPROM and ETHTOOL_SEEPROM interface and abusing it to
> implement a non-standard interface that is custom to the out-of-tree Intel
> drivers to support the flash update utility.
>
> This implementation was widely rejected when
On Sun, Jun 09, 2024 at 05:33:54PM +, Asbjørn Sloth Tønnesen wrote:
> Encapsulation control flags are currently not used anywhere,
> so all flags are currently unsupported by all drivers.
>
> This patch adds validation of this assumption, so that
> encapsulation flags may be used in the future
On Tue, Jun 11, 2024 at 01:59:37PM +0200, Alexander Lobakin wrote:
> From: Maciej Fijalkowski
> Date: Tue, 4 Jun 2024 15:21:48 +0200
>
> > From: Michal Kubiak
> >
> > Address a scenario in which XSK ZC Tx produces descriptors to XDP Tx
> > ring when link is either not yet fully initialized or
On Tue, Jun 11, 2024 at 02:22:37PM +0100, Mark Brown wrote:
> On Tue, Jun 11, 2024 at 03:01:04PM +0200, Greg Kroah-Hartman wrote:
> > In the quest to make struct device constant, start by making
> > to_auziliary_drv() return a constant pointer so that drivers that call
> > this can be fixed up befo
On Tue, Jun 11, 2024 at 01:44:07PM +, Sakari Ailus wrote:
> Hi Greg,
>
> On Tue, Jun 11, 2024 at 03:01:04PM +0200, Greg Kroah-Hartman wrote:
> > In the quest to make struct device constant, start by making
> > to_auziliary_drv() return a constant pointer so that drivers that call
>
> s/z/s/
On 6/11/24 15:01, Greg Kroah-Hartman wrote:
In the quest to make struct device constant, start by making
just curious, how far it will go? eg. do you plan to convert
get/put_device() to accept const? or convert devlink API to accept
consts?
to_auziliary_drv() return a constant pointer so that
In the quest to make struct device constant, start by making
to_auziliary_drv() return a constant pointer so that drivers that call
this can be fixed up before the driver core changes.
As the return type previously was not constant, also fix up all callers
that were assuming that the pointer was n
From: Maciej Fijalkowski
Date: Tue, 4 Jun 2024 15:21:48 +0200
> From: Michal Kubiak
>
> Address a scenario in which XSK ZC Tx produces descriptors to XDP Tx
> ring when link is either not yet fully initialized or process of
> stopping the netdev has already started. To avoid this, add checks
>
From: Mateusz Polchlopek
Date: Tue, 4 Jun 2024 09:13:57 -0400
> From: Jacob Keller
>
> Using VIRTCHNL_VF_OFFLOAD_FLEX_DESC, the iAVF driver is capable of
> negotiating to enable the advanced flexible descriptor layout. Add the
> flexible NIC layout (RXDID=2) as a member of the Rx descriptor un
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git
dev-queue
head: 10d0e5f67bf964e5e8cc7a99ab8c1942ce3d97c7
commit: cad731b65625243ce2b7b83375ab76c7828398be [65/95] iavf: periodically
cache PHC time
config: riscv-randconfig-002-20240611
(https://download.01.org/0day
> -Original Message-
> From: Intel-wired-lan On Behalf Of
> jackie.j...@alliedtelesis.co.nz
> Sent: Tuesday, June 4, 2024 8:40 AM
> To: da...@davemloft.net
> Cc: jackie.j...@alliedtelesis.co.nz; net...@vger.kernel.org;
> linux-ker...@vger.kernel.org; Nguyen, Anthony L ;
> chris.pack...@
From: David Decotigny
Date: Tue, 4 Jun 2024 16:34:48 -0700
>
>
> On 6/3/2024 11:47 AM, Joshua Hay wrote:
>>
>> There are several reasons for a TX completion to take longer than usual
>> to be written back by HW. For example, the completion for a packet that
>> misses a rule will have increased
Dear Eric, dear Karen,
Thank you for the patch.
Am 28.05.24 um 11:01 schrieb Karen Ostrowska:
From: Eric Joyner
Check the return value from ice_vsi_rebuild() and prevent the usage of
incorrectly configured VSI.
Was this found during code review, or is this seen in practice? If the
latter
The bug affects users ionly at the time when they try to update NVM, and
only F/W versions that generate errors while nvmupdate. For example X710DA2
with 0x8000ECB7 F/W is affected, but there are probably more...
After 230f3d53a547 patch, which should only replace F/W specific error codes
into Lin
> -Original Message-
> From: Paul Menzel
> Sent: Monday, June 10, 2024 2:26 PM
> To: Loktionov, Aleksandr ; Kang, Kelvin
>
> Cc: Sokolowski, Jan ; net...@vger.kernel.org;
> Kubalewski, Arkadiusz ; Nguyen, Anthony L
> ; intel-wired-...@lists.osuosl.org; Leon
> Romanovsky
> Subject: Re:
26 matches
Mail list logo
