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
| ||
|
Message-Id: <166389361666.358.15863956184982535662.git-patchwork-notify@kernel.org> Date: Fri, 23 Sep 2022 00:40:16 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Vadim Fedorenko <vfedorenko@...ek.ru> Cc: michael.chan@...adcom.com, pavan.chebbi@...adcom.com, netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net, richardcochran@...il.com Subject: Re: [PATCH net-next v3] bnxt_en: replace reset with config timestamps Hello: This patch was applied to netdev/net-next.git (master) by Jakub Kicinski <kuba@...nel.org>: On Thu, 22 Sep 2022 22:10:38 +0300 you wrote: > Any change to the hardware timestamps configuration triggers nic restart, > which breaks transmition and reception of network packets for a while. > But there is no need to fully restart the device because while configuring > hardware timestamps. The code for changing configuration runs after all > of the initialisation, when the NIC is actually up and running. This patch > changes the code that ioctl will only update configuration registers and > will not trigger carrier status change, but in case of timestamps for > all rx packetes it fallbacks to close()/open() sequnce because of > synchronization issues in the hardware. Tested on BCM57504. > > [...] Here is the summary with links: - [net-next,v3] bnxt_en: replace reset with config timestamps https://git.kernel.org/netdev/net-next/c/8db3d514e967 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists