Commit d25e92d2 authored by Wang Jinchao's avatar Wang Jinchao Committed by Jonathan Corbet
Browse files

memory-hotplug.rst: fix wrong /sys/device/ path 



Actually, it should be /sys/devices/

Signed-off-by: default avatarWang Jinchao <wangjinchao@xfusion.com>
Reviewed-by: default avatarDavid Hildenbrand <david@redhat.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
Message-ID: <ZQz1NUATBMOb3RT+@fedora>
parent 86a0adc0

Documentation/admin-guide/mm/memory-hotplug.rst

+4 −4
Original line number Diff line number Diff line
@@ -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)