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: <20231001122334.GM92317@kernel.org> Date: Sun, 1 Oct 2023 14:23:34 +0200 From: Simon Horman <horms@...nel.org> To: Markus Schneider-Pargmann <msp@...libre.com> Cc: Marc Kleine-Budde <mkl@...gutronix.de>, Chandrasekar Ramakrishnan <rcsekar@...sung.com>, Wolfgang Grandegger <wg@...ndegger.com>, Vincent MAILHOL <mailhol.vincent@...adoo.fr>, "David S . Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, linux-can@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Julien Panis <jpanis@...libre.com>, Judith Mendez <jm@...com> Subject: Re: [PATCH v6 05/14] can: m_can: Implement transmit coalescing On Fri, Sep 29, 2023 at 04:12:55PM +0200, Markus Schneider-Pargmann wrote: > Extend the coalescing implementation for transmits. > > In normal mode the chip raises an interrupt for every finished transmit. > This implementation switches to coalescing mode as soon as an interrupt > handled a transmit. For coalescing the watermark level interrupt is used > to interrupt exactly after x frames were sent. It switches back into > normal mode once there was an interrupt with no finished transmit and > the timer being inactive. > > The timer is shared with receive coalescing. The time for receive and > transmit coalescing timers have to be the same for that to work. The > benefit is to have only a single running timer. > > Signed-off-by: Markus Schneider-Pargmann <msp@...libre.com> Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists