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: <ZCL9a5kXqMCx7n7L@corigine.com> Date: Tue, 28 Mar 2023 16:44:59 +0200 From: Simon Horman <simon.horman@...igine.com> To: Hariprasad Kelam <hkelam@...vell.com> Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, kuba@...nel.org, davem@...emloft.net, willemdebruijn.kernel@...il.com, andrew@...n.ch, sgoutham@...vell.com, lcherian@...vell.com, gakula@...vell.com, jerinj@...vell.com, sbhatta@...vell.com, naveenm@...vel.com, edumazet@...gle.com, pabeni@...hat.com, jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us, maxtram95@...il.com Subject: Re: [net-next Patch v5 4/6] octeontx2-pf: Refactor schedular queue alloc/free calls On Sun, Mar 26, 2023 at 11:42:43PM +0530, Hariprasad Kelam wrote: > Multiple transmit scheduler queues can be configured at different > levels to support traffic shaping and scheduling. But on txschq free > requests, the transmit schedular config in hardware is not getting > reset. This patch adds support to reset the stale config. > > The txschq alloc response handler updates the default txschq > array which is used to configure the transmit packet path from > SMQ to TL2 levels. However, for new features such as QoS offload > that requires it's own txschq queues, this handler is still > invoked and results in undefined behavior. The code now handles > txschq response in the mbox caller function. > > Signed-off-by: Hariprasad Kelam <hkelam@...vell.com> > Signed-off-by: Naveen Mamindlapalli <naveenm@...vell.com> > Signed-off-by: Sunil Kovvuri Goutham <sgoutham@...vell.com> Reviewed-by: Simon Horman <simon.horman@...igine.com>
Powered by blists - more mailing lists