* [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path
@ 2023-09-22 2:00 Wang Jinchao
2023-09-22 7:33 ` David Hildenbrand
2023-09-22 11:19 ` Jonathan Corbet
0 siblings, 2 replies; 3+ messages in thread
From: Wang Jinchao @ 2023-09-22 2:00 UTC (permalink / raw)
To: David Hildenbrand, Oscar Salvador, Jonathan Corbet, linux-mm,
linux-doc, linux-kernel
Cc: xulei
Actually, it should be /sys/devices/
Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
---
Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
1 file 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)
--
2.40.0
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path
2023-09-22 2:00 [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path Wang Jinchao
@ 2023-09-22 7:33 ` David Hildenbrand
2023-09-22 11:19 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: David Hildenbrand @ 2023-09-22 7:33 UTC (permalink / raw)
To: Wang Jinchao, Oscar Salvador, Jonathan Corbet, linux-mm,
linux-doc, linux-kernel
Cc: xulei
On 22.09.23 04:00, Wang Jinchao wrote:
> Actually, it should be /sys/devices/
>
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
> Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
> 1 file 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)
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path
2023-09-22 2:00 [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path Wang Jinchao
2023-09-22 7:33 ` David Hildenbrand
@ 2023-09-22 11:19 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2023-09-22 11:19 UTC (permalink / raw)
To: Wang Jinchao, David Hildenbrand, Oscar Salvador, linux-mm,
linux-doc, linux-kernel
Cc: xulei
Wang Jinchao <wangjinchao@xfusion.com> writes:
> Actually, it should be /sys/devices/
>
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
> Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-09-22 11:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-09-22 2:00 [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path Wang Jinchao
2023-09-22 7:33 ` David Hildenbrand
2023-09-22 11:19 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox