Currently locking for memory hotplug is a little complicated.
Generally speaking, we leverage the two global lock:
* device_hotplug_lock
* mem_hotplug_lock
to serialise the process.
While for the long term, we are willing to have more fine-grained lock
to provide higher scalability.
This
Locking Internal section exists in core-api documentation, which is more
suitable for this.
This patch removes the duplication part here.
Signed-off-by: Wei Yang
---
Documentation/admin-guide/mm/memory-hotplug.rst | 40 -
1 file changed, 40 deletions(-)
diff --git
