netdev - Re: [PATCH net-next] r8169: enable ASPM L0s state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <162979920578.20108.1098485712755805990.git-patchwork-notify@kernel.org>
Date:   Tue, 24 Aug 2021 10:00:05 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Heiner Kallweit <hkallweit1@...il.com>
Cc:     kuba@...nel.org, davem@...emloft.net, nic_swsd@...ltek.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next] r8169: enable ASPM L0s state

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Tue, 24 Aug 2021 08:23:20 +0200 you wrote:
> ASPM is disabled completely because we've seen different types of
> problems in the past. However it seems these problems occurred with
> L1 or L1 sub-states only. On all the chip versions I've seen the
> acceptable L0s exit latency is 512ns. This should be short enough not
> to cause problems. If the actual L0s exit latency of the PCIe link
> is bigger than 512ns then the PCI core will disable L0s anyway.
> So let's give it a try and disable L1 and L1 sub-states only.
> 
> [...]

Here is the summary with links:
  - [net-next] r8169: enable ASPM L0s state
    https://git.kernel.org/netdev/net-next/c/18a9eae240cb

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html