Hi Svetly, On Tue, Apr 02, 2024 at 01:26:35PM GMT, Svetly Todorov wrote: > > > --- > Adding documentation for the new MPOL_WEIGHTED_INTERLEAVE mode in the same > manpages that mention MPOL_INTERLEAVE; namely, mbind(2), set_mempolicy(2), > and get_mempolicy(2). > > Descriptions were based on the changes introduced in this patch: > https://lore.kernel.org/all/20240202170238.90004-4-gregory.price@xxxxxxxxxxxx/ > > Which was upstreamed to 6.9 here: > https://lore.kernel.org/linux-mm/20240313200532.34e4cff216acd3db8def4637@xxxxxxxxxxxxxxxxxxxx/ > > To: alx@xxxxxxxxxx > Cc: linux-man@xxxxxxxxxxxxxxx > Cc: gregory.price@xxxxxxxxxxxx > Cc: ying.huang@xxxxxxxxx > Reviewed-by: "Huang, Ying" <ying.huang@xxxxxxxxx> > Signed-off-by: Svetly Todorov <svetly.todorov@xxxxxxxxxxxx> [...] > @@ -243,6 +244,23 @@ at least 1\ MB or bigger with a fairly uniform access pattern. > Accesses to a single page of the area will still be limited to > the memory bandwidth of a single node. > .TP > +.BR MPOL_WEIGHTED_INTERLEAVE " (since Linux 6.9)" > +.\" commit fa3bea4e1f8202d787709b7e3654eb0a99aed758 > +This mode interleaves page allocations across the nodes specified in > +.I nodemask > +according to the weights in > +.IR /sys/kernel/mm/mempolicy/weighted_interleave . > +For example, if bits 0, 2, and 5 are raised in I've checked that there's no other use of "raise" for saying that a bit is set, in the Linux man-pages project (or I couldn't find it). Let's say "set", which is far more common, I think. > +.IR nodemask , > +and the contents of > +.IR /sys/kernel/mm/mempolicy/weighted_interleave/node0 , > +.IR /sys/ .\|.\|. /node2 , > +and > +.IR /sys/ .\|.\|. /node5 > +are 4, 7, and 9, respectively, > +then pages in this region will be allocated on nodes 0, 2, and 5 > +in a 4:7:9 ratio. > +.TP > .B MPOL_PREFERRED > This mode sets the preferred node for allocation. > The kernel will try to allocate pages from this > diff --git a/man2/set_mempolicy.2 b/man2/set_mempolicy.2 > index fc3ad9df8..3c08b6bf0 100644 > --- a/man2/set_mempolicy.2 > +++ b/man2/set_mempolicy.2 > @@ -63,6 +63,7 @@ argument must specify one of > .BR MPOL_DEFAULT , > .BR MPOL_BIND , > .BR MPOL_INTERLEAVE , > +.BR MPOL_WEIGHTED_INTERLEAVE , > .BR MPOL_PREFERRED , > or > .B MPOL_LOCAL > @@ -199,6 +200,23 @@ the memory bandwidth of a single node. > .\" To be effective the memory area should be fairly large, > .\" at least 1 MB or bigger. > .TP > +.BR MPOL_WEIGHTED_INTERLEAVE " (since Linux 6.9)" > +.\" commit fa3bea4e1f8202d787709b7e3654eb0a99aed758 > +This mode interleaves page allocations across the nodes specified in > +.I nodemask > +according to the weights in > +.IR /sys/kernel/mm/mempolicy/weighted_interleave . > +For example, if bits 0, 2, and 5 are raised in Same here. Other than that, the patch LGTM. Thanks! Have a lovely day! Alex > +.IR nodemask , > +and the contents of > +.IR /sys/kernel/mm/mempolicy/weighted_interleave/node0 , > +.IR /sys/ .\|.\|. /node2 , > +and > +.IR /sys/ .\|.\|. /node5 > +are 4, 7, and 9, respectively, > +then pages in this region will be allocated on nodes 0, 2, and 5 > +in a 4:7:9 ratio. > +.TP > .B MPOL_PREFERRED > This mode sets the preferred node for allocation. > The kernel will try to allocate pages from this node first > > --- > base-commit: a4ea5f76215dcf1d8d017eb65ab12919ccf09f3f > change-id: 20240313-weighted_interleave-e8141ed754f9 > > Best regards, > -- > Svetly Todorov <svetly.todorov@xxxxxxxxxxxx> > -- <https://www.alejandro-colomar.es/>
Attachment:
signature.asc
Description: PGP signature
