v3 De-couple sysfs memory directories from memory sections
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest8 patches 21 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | v3 Move the find_memory_block() routine updrivers/ | +31 | 1 reply | |
| 2/8 | v3 Add new phys_index propertiesdrivers/ include/ | +24 | 3 replies | |
| 3/8 | v3 Add section count to memory_blockdrivers/ include/ | +14 | 2 replies | |
| 4/8 | v3 Allow memory_block to span multiple memory sectionsdrivers/ | +98 | 7 replies | |
| 5/8 | v3 Update the find_memory_block declarationinclude/ | +1 | 1 reply | |
| 6/8 | v3 Update the node sysfs codedrivers/ drivers/ include/ | +11 | 2 replies | |
| 7/8 | v3 Define memory_block_size_bytes() for ppc/pseriesarch/ | +53 | 1 reply | |
| 8/8 | v3 Update memory-hotplug documentationDocumentation/ | +24 | 1 reply |
Reviews trailers per patch
2 of 8 patches have a Reviewed-by or Acked-by.
| Patch | KAMEZAWA Hiroyuki |
|---|---|
| 1/8 | A-b |
| 2/8 | |
| 3/8 | |
| 4/8 | |
| 5/8 | Reviewd-by |
| 6/8 | A-b |
| 7/8 | |
| 8/8 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/8] v3 De-couple sysfs memory directories from memory sections
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.
-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>