git: 39d4ccf82607 - main - zone.9: Remove documentation of non-existent NUMA configuration flags

The branch main has been updated by markj:

URL: https://cgit.FreeBSD.org/src/commit/?id=39d4ccf82607c99655fda0d76357a7f534fa724f

commit 39d4ccf82607c99655fda0d76357a7f534fa724f
Author:     Mark Johnston <markj@FreeBSD.org>
AuthorDate: 2022-01-14 20:02:07 +0000
Commit:     Mark Johnston <markj@FreeBSD.org>
CommitDate: 2022-01-14 20:02:07 +0000

    zone.9: Remove documentation of non-existent NUMA configuration flags
    
    These configuration options were removed in commit dfe13344f557.
    
    Some forthcoming work will update the UMA man page to describe its
    current behaviour on NUMA systems.
    
    MFC after:      1 week
    Sponsored by:   The FreeBSD Foundation
---
 share/man/man9/zone.9 | 20 --------------------
 1 file changed, 20 deletions(-)

diff --git a/share/man/man9/zone.9 b/share/man/man9/zone.9
index 77776c50bc5d..cae76dbc6ff7 100644
--- a/share/man/man9/zone.9
+++ b/share/man/man9/zone.9
@@ -35,8 +35,6 @@
 .In sys/param.h
 .In sys/queue.h
 .In vm/uma.h
-.Cd "options UMA_FIRSTTOUCH"
-.Cd "options UMA_XDOMAIN"
 .Bd -literal
 typedef int (*uma_ctor)(void *mem, int size, void *arg, int flags);
 typedef void (*uma_dtor)(void *mem, int size, void *arg);
@@ -322,24 +320,6 @@ The zone is for the
 subsystem.
 .It Dv UMA_ZONE_VM
 The zone is for the VM subsystem.
-.It Dv UMA_ZONE_NUMA
-The zone should use a first-touch NUMA policy rather than the round-robin
-default.
-If the
-.Dv UMA_FIRSTTOUCH
-kernel option is configured, all zones implicitly use a first-touch policy,
-and the
-.Dv UMA_ZONE_NUMA
-flag has no effect.
-The
-.Dv UMA_XDOMAIN
-kernel option, when configured, causes UMA to do the extra tracking to ensure
-that allocations from first-touch zones are always local.
-Otherwise, consumers that do not free memory on the same domain from which it
-was allocated will cause mixing in per-CPU caches.
-See
-.Xr numa 4
-for more details.
 .It Dv UMA_ZONE_CONTIG
 Items in this zone must be contiguous in physical address space.
 Items will follow normal alignment constraints and may span page boundaries