diff options
| author | Wang Jinchao <wangjinchao@xfusion.com> | 2023-09-22 10:00:21 +0800 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2023-09-22 05:19:14 -0600 |
| commit | d25e92d2aed9cdff2a2222e82412a53f70e17c1a (patch) | |
| tree | f50929ae00c4b2b34bc051b3ed6ecdc818282859 | |
| parent | 86a0adc029d338f0da8989e7bb453c1114d51960 (diff) | |
memory-hotplug.rst: fix wrong /sys/device/ path
Actually, it should be /sys/devices/
Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <ZQz1NUATBMOb3RT+@fedora>
| -rw-r--r-- | Documentation/admin-guide/mm/memory-hotplug.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst index cfe034cf1e87..01595965734a 100644 --- a/Documentation/admin-guide/mm/memory-hotplug.rst +++ b/Documentation/admin-guide/mm/memory-hotplug.rst @@ -250,15 +250,15 @@ Observing the State of Memory Blocks The state (online/offline/going-offline) of a memory block can be observed either via:: - % cat /sys/device/system/memory/memoryXXX/state + % cat /sys/devices/system/memory/memoryXXX/state Or alternatively (1/0) via:: - % cat /sys/device/system/memory/memoryXXX/online + % cat /sys/devices/system/memory/memoryXXX/online For an online memory block, the managing zone can be observed via:: - % cat /sys/device/system/memory/memoryXXX/valid_zones + % cat /sys/devices/system/memory/memoryXXX/valid_zones Configuring Memory Hot(Un)Plug ============================== @@ -326,7 +326,7 @@ however, a memory block might span memory holes. A memory block spanning memory holes cannot be offlined. For example, assume 1 GiB memory block size. A device for a memory starting at -0x100000000 is ``/sys/device/system/memory/memory4``:: +0x100000000 is ``/sys/devices/system/memory/memory4``:: (0x100000000 / 1Gib = 4) |