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] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zlfx5Rq-eru82XXj@x130.lan>
Date: Wed, 29 May 2024 20:26:29 -0700
From: Saeed Mahameed <saeed@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Tariq Toukan <tariqt@...dia.com>,
	"David S. Miller" <davem@...emloft.net>,
	Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>,
	netdev@...r.kernel.org, Saeed Mahameed <saeedm@...dia.com>,
	Gal Pressman <gal@...dia.com>, Leon Romanovsky <leonro@...dia.com>,
	Yoray Zack <yorayz@...dia.com>
Subject: Re: [PATCH net-next 13/15] net/mlx5e: SHAMPO, Use KSMs instead of
 KLMs

On 29 May 18:23, Jakub Kicinski wrote:
>On Tue, 28 May 2024 17:28:05 +0300 Tariq Toukan wrote:
>> KSM Mkey is KLM Mkey with a fixed buffer size. Due to this fact,
>> it is a faster mechanism than KLM.
>>
>> SHAMPO feature used KLMs Mkeys for memory mappings of its headers buffer.
>> As it used KLMs with the same buffer size for each entry,
>> we can use KSMs instead.
>>
>> This commit changes the Mkeys that map the SHAMPO headers buffer
>> from KLMs to KSMs.
>
>Any references for understanding what KSM and KLM stand for?
>

Not available publicly. Simply those are two different HW mechanisms to
translate HW virtual to physical addresses. KSM assumes fixed buffer
length, hence performs faster.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ