cgroups.7: Improve the discussion of the advantages of v2 release notification

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man7/cgroups.7 b/man7/cgroups.7
index e1dfaca2d6cf680027e66a3ff123867094b89bf7..73cd468b0b34ec9e221201e24cd16640edc9fa2d 100644 (file)
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -835,17 +835,21 @@ or 1, meaning that the cgroup (or one of its descendants)
 contains member processes.
 .PP
 The cgroups v2 release-notification mechanism
-offers at least two advantages over the cgroups v1
+offers the following advantages over the cgroups v1
 .IR release_agent
-mechanism.
-First, it allows for cheaper notification,
+mechanism:
+.IP * 3
+It allows for cheaper notification,
 since a single process can monitor multiple
 .IR cgroup.events
 files (using the techniques described earlier).
-By contrast, the cgroups v1 mechanism requires the creation
-of a process for each notification.
-Second, notification can be delegated to a process that lives inside
-a container associated with the newly empty cgroup.
+By contrast, the cgroups v1 mechanism requires the expense of creating
+a process for each notification.
+.IP *
+Notification for different cgroup subhierarchies can be delegated
+to different processes.
+By contrast, the cgroups v1 mechanism allows only one release agent
+for an entire hierarchy.
 .\"
 .SS Cgroups v2 cgroup.stat file
 .\" commit ec39225cca42c05ac36853d11d28f877fde5c42e