@@ -37,7 +37,7 @@ Every ``{}`` in the path is replaced with an extra argument passed to the CTL
3737function. Alternative addressing methods are described below.
3838
3939Pool / Provider addressing
40- ==========================
40+ ============================
4141
4242Two addressing schemes are provided: ``by_handle `` and ``by_name ``. Each pool
4343and provider has a unique handle and an optional user-defined name that can be
@@ -56,7 +56,7 @@ appending an index after the name::
5656The number of pools with a given name can be obtained with the ``count `` node.
5757
5858Wildcards
59- =========
59+ ===========
6060
6161A ``{} `` in the path acts as a wildcard and is replaced with successive
6262arguments of ``umfCtlGet ``, ``umfCtlSet `` or ``umfCtlExec ``. Wildcards can
@@ -74,18 +74,21 @@ replace any node, not only handles. For example::
7474Ensure that the types of wildcard arguments match the expected node types.
7575
7676Default addressing
77- ==================
77+ ===================
7878
7979``umf.provider.default `` and ``umf.pool.default `` store default values applied
8080to providers or pools created after the defaults are set. For example::
8181
82- const char *name = "custom";
83- umfCtlSet("umf.pool.default.disjoint.name", (void *)name, strlen(name)+1);
82+ size_t capacity = 16;
83+ umfCtlSet("umf.pool.default.disjoint.params.capacity", &capacity,
84+ sizeof(capacity));
8485
85- Every subsequently created disjoint pool will use ``custom `` as its name unless
86- overridden by explicit parameters. Defaults may be supplied programmatically or
87- via configuration and are saved internally and applied during initalization of
88- a matching provider or pool.
86+ Every subsequently created disjoint pool will use ``16 `` as its starting
87+ capacity overriding it's creation parameters. Defaults are keyed by the
88+ name returned from the provider or pool ``get_name `` callback, so if pool/provider
89+ has custom name it must be addressed explicitly. Defaults may be supplied programmatically
90+ or via environment variable and are saved internally and applied during initialization of a
91+ matching provider or pool.
8992
9093Environment variables
9194=====================
@@ -771,7 +774,7 @@ these entries.
771774>>>>>>> da1363dd (better documentation)
772775
773776Reading this reference
774- ----------------------
777+ =======================
775778
776779Parameter annotations describe the values stored in the node rather than the
777780pointer types passed to ``umfCtlGet ``/``umfCtlSet ``/``umfCtlExec ``. The
@@ -841,7 +844,7 @@ Logger nodes
841844
842845 :param path: Receives the currently selected sink on reads. On writes, pass
843846 ``"stdout" `` or ``"stderr" `` to redirect to standard streams, a
844- NUL -terminated file path to append to a file, or ``NULL `` to disable
847+ NULL -terminated file path to append to a file, or ``NULL `` to disable
845848 logging altogether.
846849 :type path: ``char * `` when reading, ``const char * `` when writing
847850
@@ -862,14 +865,14 @@ Provider entries are organized beneath ``umf.provider``. Use
862865``umf.provider.by_handle.{provider} `` with a
863866:type: `umf_memory_provider_handle_t ` argument to reach a specific provider.
864867Providers can also be addressed by name through ``umf.provider.by_name.{provider} ``;
865- append ``.{index} `` to address specyfic provider when multiple providers share the same label.
866- Defaults for future providers live under ``umf.provider.default.{provider_name } ``,
867- where `` {provider_name} `` matches the canonical provider identifier (`` OS ``,
868- `` FILE ``, ``DEVDAX ``, ``FIXED ``, ``CUDA `` or ``LEVEL_ZERO ``). Values written to
869- the default tree are saved until a matching provider is created and applied
870- during provider initialization. Defaults can be supplied programmatically or
871- through configuration strings. The entries below list only the suffix of each
872- node; prefix them with the appropriate ``umf.provider `` path.
868+ append ``.{index} `` to address specific provider when multiple providers share the same label.
869+ Defaults for future providers reside under ``umf.provider.default.{provider } `` and track the
870+ name returned by each provider's `` get_name `` implementation. Providers have their
871+ default names (`` OS ``, `` FILE ``, ``DEVDAX ``, ``FIXED ``, ``CUDA `` or ``LEVEL_ZERO ``),
872+ unless their name was changed during creation, those renamed providers must be addressed explicitly.
873+ Defaults can be written via `` umf.provider.default.<name> `` either programmatically or through
874+ configuration strings. The entries below list only the suffix of each node;
875+ prefix them with the appropriate ``umf.provider `` path.
873876
874877Common provider statistics
875878--------------------------
@@ -971,11 +974,13 @@ Pool nodes
971974Pool entries mirror the provider layout. ``umf.pool.by_handle.{pool} `` accepts a
972975:type: `umf_memory_pool_handle_t `, while ``umf.pool.by_name.{pool} `` addresses
973976pools by name with an optional ``.{index} `` suffix when names are reused.
974- Defaults for future pools reside under ``umf.pool.default.{pool} ``, where
975- canonical names include ``disjoint ``, ``scalable `` and ``jemalloc ``. Defaults
976- can be written via ``umf.pool.default.<pool> `` either programmatically or
977- through configuration strings. The entries below list only the suffix of each
978- node; prefix them with the appropriate ``umf.pool `` path.
977+ Defaults for future pools reside under ``umf.pool.default.{pool} `` and track the
978+ name returned by each pool's ``get_name `` implementation. Pools that keep their
979+ default names (``disjoint ``, ``scalable `` and ``jemalloc ``) continue to match
980+ those entries, while renamed pools must be addressed explicitly. Defaults can be
981+ written via ``umf.pool.default.<pool> `` either programmatically or through
982+ configuration strings. The entries below list only the suffix of each node;
983+ prefix them with the appropriate ``umf.pool `` path.
979984
980985Common pool statistics
981986--------------------------
@@ -1001,7 +1006,7 @@ Disjoint pool (``disjoint``)
10011006 provider.
10021007 :type bytes: ``size_t ``
10031008
1004- **Access: ** read-write. (write is only avaiable through defaults)
1009+ **Access: ** read-write. (write is only available through defaults)
10051010 **Defaults / Env: ** supported.
10061011
10071012 Governs how much memory the pool grabs in each slab. Lower values reduce
@@ -1014,7 +1019,7 @@ Disjoint pool (``disjoint``)
10141019 cached by the pool.
10151020 :type bytes: ``size_t ``
10161021
1017- **Access: ** read-write. (write is only avaiable through defaults)
1022+ **Access: ** read-write. (write is only available through defaults)
10181023 **Defaults / Env: ** supported.
10191024
10201025 Sets the cut-off for pooling allocations. Requests larger than this value are
@@ -1027,7 +1032,7 @@ Disjoint pool (``disjoint``)
10271032 may retain.
10281033 :type count: ``size_t ``
10291034
1030- **Access: ** read-write. (write is only avaiable through defaults)
1035+ **Access: ** read-write. (write is only available through defaults)
10311036 **Defaults / Env: ** supported.
10321037
10331038 Caps the pool's cached slabs per bucket to limit memory retention. Shrinking
@@ -1040,7 +1045,7 @@ Disjoint pool (``disjoint``)
10401045 serve.
10411046 :type bytes: ``size_t ``
10421047
1043- **Access: ** read-write. (write is only avaiable through defaults)
1048+ **Access: ** read-write. (write is only available through defaults)
10441049 **Defaults / Env: ** supported.
10451050
10461051 Controls the smallest chunk size kept in the pool, which in turn affects the
@@ -1052,7 +1057,7 @@ Disjoint pool (``disjoint``)
10521057 :param level: Receives or supplies the tracing level for the pool.
10531058 :type level: ``int `` (``0 `` disables tracing)
10541059
1055- **Access: ** read-write. (write is only avaiable through defaults)
1060+ **Access: ** read-write. (write is only available through defaults)
10561061 **Defaults / Env: ** supported.
10571062
10581063 Controls the disjoint pool's tracing features. ``0 `` disables tracing.
0 commit comments