Skip to content

v2 De-couple sysfs memory directories from memory section size

Nathan Fontenot linux-mm linuxppc-dev lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 12 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5v2 Split the memory_block structuredrivers/base/memory.c include/linux/memory.h+167 -666 replies
2/5v2 Create new 'end_phys_index' filedrivers/base/memory.c include/linux/memory.h+16 -12 replies
3/5v2 Change the mutex name in the memory_block structdrivers/base/memory.c include/linux/memory.h+11 -181 reply
4/5v2 Update sysfs node routines for new sysfs memory directoriesdrivers/base/node.c+8 -42 replies
5/5v2 Enable multiple sections per directory for ppcarch/powerpc/platforms/pseries/hotplug-memory.c+53 -131 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/5] v2 De-couple sysfs memory directories from memory section size

This set of patches de-couples the idea that there is a single directory in sysfs for each memory section. The intent of the patches is to reduce the number of sysfs directories created to resolve a boot-time performance issue. On very large systems boot time are getting very long (as seen on powerpc hardware) due to the enormous number of sysfs directories being created. On a system with 1 TB of memory we create ~63,000 directories. For even larger systems boot times are being measured in hours.

This set of patches allows for each directory created in sysfs to cover more than one memory section. The default behavior for sysfs directory creation is the same, in that each directory represents a single memory section. A new file 'end_phys_index' in each directory contains the physical_id of the last memory section covered by the directory so that users can easily determine the memory section range of a directory.

For version 2 of this patchset the capability to split a directory has been removed.

Thanks,

Nathan Fontenot

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>