[v4,0/2] ksm: count allocated rmap_items and update documentation

Message

CGEL Aug. 24, 2022, 12:45 p.m. UTC

KSM can save memory by merging identical pages, but also can consume
additional memory, because it needs to generate rmap_items to save
each scanned page's brief rmap information.

To determine how beneficial the ksm-policy (like madvise), they are using
brings, so we add a new interface /proc/<pid>/ksm_alloced_items for each
process to indicate the total allocated ksm rmap_items of this process.

The detailed description can be seen in the following patches' commit message.


-----------
v3->v4:
Fix the wrong writing format and some misspellings of the related documentaion.

v2->v3:
remake the patches based on the latest linux-next branch.

v1->v2:
Add documentation for the new item.



*** BLURB HERE ***

xu xin (2):
  ksm: count allocated ksm rmap_items for each process
  ksm: add profit monitoring documentation

 Documentation/admin-guide/mm/ksm.rst | 36 ++++++++++++++++++++++++++++
 fs/proc/base.c                       | 15 ++++++++++++
 include/linux/mm_types.h             |  5 ++++
 mm/ksm.c                             |  2 ++
 4 files changed, 58 insertions(+)


base-commit: 68a00424bf69036970ced7930f9e4d709b4a6423

Comments

Matthew Wilcox Aug. 24, 2022, 12:56 p.m. UTC | #1

On Wed, Aug 24, 2022 at 12:45:12PM +0000, xu xin wrote:
> v3->v4:
> Fix the wrong writing format and some misspellings of the related documentaion.
> 
> v2->v3:
> remake the patches based on the latest linux-next branch.
> 
> v1->v2:
> Add documentation for the new item.

Don't send multiple versions of a patch series per day.  This fragments
review and makes it harder to know what's going on with the patch series.
Leave it at least a day between versions, preferably a week.