Home » Mailing list archives » linux-kernel » 2010 » August » 3

[PATCH 9/9] v4 Update memory-hotplug documentation

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Nathan Fontenot
Subject: [PATCH 9/9] v4 Update memory-hotplug documentation
Date: Tuesday, August 3, 2010 - 6:44 am

Update the memory hotplug documentation to reflect the new behaviors of
memory blocks reflected in sysfs.

Signed-off-by: Nathan Fontenot <nfont@austin.ibm.com>
---
 Documentation/memory-hotplug.txt |   40 +++++++++++++++++++++++----------------
 1 file changed, 24 insertions(+), 16 deletions(-)

Index: linux-2.6/Documentation/memory-hotplug.txt
===================================================================
--- linux-2.6.orig/Documentation/memory-hotplug.txt	2010-08-02 14:09:28.000000000 -0500
+++ linux-2.6/Documentation/memory-hotplug.txt	2010-08-02 14:10:36.000000000 -0500
@@ -126,36 +126,44 @@ config options.
 --------------------------------
 4 sysfs files for memory hotplug
 --------------------------------
-All sections have their device information under /sys/devices/system/memory as
+All sections have their device information in sysfs.  Each section is part of
+a memory block under /sys/devices/system/memory as
 
 /sys/devices/system/memory/memoryXXX
-(XXX is section id.)
+(XXX is the section id.)
 
-Now, XXX is defined as start_address_of_section / section_size.
+Now, XXX is defined as (start_address_of_section / section_size) of the first
+section contained in the memory block.
 
 For example, assume 1GiB section size. A device for a memory starting at
 0x100000000 is /sys/device/system/memory/memory4
 (0x100000000 / 1Gib = 4)
 This device covers address range [0x100000000 ... 0x140000000)
 
-Under each section, you can see 4 files.
+Under each section, you can see 5 files.
 
-/sys/devices/system/memory/memoryXXX/phys_index
+/sys/devices/system/memory/memoryXXX/start_phys_index
+/sys/devices/system/memory/memoryXXX/end_phys_index
 /sys/devices/system/memory/memoryXXX/phys_device
 /sys/devices/system/memory/memoryXXX/state
 /sys/devices/system/memory/memoryXXX/removable
 
-'phys_index' : read-only and contains section id, same as XXX.
-'state'      : read-write
-               at read:  contains online/offline state of memory.
-               at write: user can specify "online", "offline" command
-'phys_device': read-only: designed to show the name of physical memory device.
-               This is not well implemented now.
-'removable'  : read-only: contains an integer value indicating
-               whether the memory section is removable or not
-               removable.  A value of 1 indicates that the memory
-               section is removable and a value of 0 indicates that
-               it is not removable.
+'phys_index'      : read-only and contains section id of the first section
+		    in the memory block, same as XXX.
+'end_phys_index'  : read-only and contains section id of the last section
+		    in the memory block.
+'state'           : read-write
+                    at read:  contains online/offline state of memory.
+                    at write: user can specify "online", "offline" command
+                    which will be performed on al sections in the block.
+'phys_device'     : read-only: designed to show the name of physical memory
+                    device.  This is not well implemented now.
+'removable'       : read-only: contains an integer value indicating
+                    whether the memory block is removable or not
+                    removable.  A value of 1 indicates that the memory
+                    block is removable and a value of 0 indicates that
+                    it is not removable. A memory block is removable only if
+                    every section in the block is removable.
 
 NOTE:
   These directories/files appear after physical memory hotplug phase.


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[PATCH 0/9] v4 De-couple sysfs memory directories from me ..., Nathan Fontenot, (Tue Aug 3, 6:32 am)
[PATCH 1/9] v4 Move the find_memory_block() routine up, Nathan Fontenot, (Tue Aug 3, 6:36 am)
[PATCH 2/9] v4 Add new phys_index properties, Nathan Fontenot, (Tue Aug 3, 6:37 am)
[PATCH 3/9] v4 Add section count to memory_block, Nathan Fontenot, (Tue Aug 3, 6:38 am)
[PATCH 4/9] v4 Add mutex for add/remove of memory blocks, Nathan Fontenot, (Tue Aug 3, 6:39 am)
[PATCH 5/9] v4 Allow memory_block to span multiple memory ..., Nathan Fontenot, (Tue Aug 3, 6:40 am)
[PATCH 6/9] v4 Update the find_memory_block declaration, Nathan Fontenot, (Tue Aug 3, 6:41 am)
[PATCH 7/9] v4 Update the node sysfs code, Nathan Fontenot, (Tue Aug 3, 6:42 am)
[PATCH 8/9] v4 Define memory_block_size_bytes() for ppc/p ..., Nathan Fontenot, (Tue Aug 3, 6:43 am)
[PATCH 9/9] v4 Update memory-hotplug documentation, Nathan Fontenot, (Tue Aug 3, 6:44 am)
Re: [PATCH 1/9] v4 Move the find_memory_block() routine up, KAMEZAWA Hiroyuki, (Wed Aug 4, 9:45 pm)
Re: [PATCH 2/9] v4 Add new phys_index properties, KAMEZAWA Hiroyuki, (Wed Aug 4, 9:49 pm)
Re: [PATCH 3/9] v4 Add section count to memory_block, KAMEZAWA Hiroyuki, (Wed Aug 4, 9:50 pm)
Re: [PATCH 4/9] v4 Add mutex for add/remove of memory blocks, KAMEZAWA Hiroyuki, (Wed Aug 4, 9:53 pm)
Re: [PATCH 5/9] v4 Allow memory_block to span multiple me ..., KAMEZAWA Hiroyuki, (Wed Aug 4, 9:55 pm)
Re: [PATCH 6/9] v4 Update the find_memory_block declaration, KAMEZAWA Hiroyuki, (Wed Aug 4, 9:59 pm)
Re: [PATCH 7/9] v4 Update the node sysfs code, KAMEZAWA Hiroyuki, (Wed Aug 4, 10:01 pm)
Re: [PATCH 9/9] v4 Update memory-hotplug documentation, KAMEZAWA Hiroyuki, (Wed Aug 4, 10:04 pm)
Re: [PATCH 4/9] v4 Add mutex for add/remove of memory blocks, Nathan Fontenot, (Mon Aug 9, 6:55 am)
Re: [PATCH 6/9] v4 Update the find_memory_block declaration, Nathan Fontenot, (Mon Aug 9, 6:56 am)