linux-kernel - Re: [PATCH 0/3] mm/ksm: Support controlling KSM with PID

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20240903043240.1776614-1-xu.xin16@zte.com.cn>
Date: Tue,  3 Sep 2024 04:32:40 +0000
From: xu xin <xu.xin.sc@...il.com>
To: shr@...kernel.io
Cc: david@...hat.com,
	linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org,
	hughd@...gle.com,
	xu.xin16@....com.cn
Subject: Re: [PATCH 0/3] mm/ksm: Support controlling KSM with PID

Hi,

In the field of embedded Linux for cost considerations, resources including
cpu and memory, are often not very sufficient, so the global deployment of
KSM can be a mitigation strategy, which is feasible for closed system
(scenarios without Internet connection). However, KSM has a side effect of
increasing write time replication latency, which is somewhat unacceptable
for latency sensitive applications. Therefore, it can be combined with the
QoS of the business tasks to dynamically close some part of those already
started processes in real time if the QoS degrade. Although it is also
beneficial for server/cloud OS, the requirement of embedded system is more
urgent and strong compared to cloud or server operating systems with
sufficient memory.