Skip to content

RFC Documentation: maple_tree: Improve statements on reserved values

Wei-Lin Chang linux-doc linux-mm lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Documentation: maple_tree: Point out constraint when using xa_{mk, to}_valueDocumentation/core-api/maple_tree.rst+5 -40 replies
2/2Documentation: maple_tree: Clarify behavior when using reserved valuesDocumentation/core-api/maple_tree.rst+2 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/2] Documentation: maple_tree: Improve statements on reserved values

Hi,

While using the maple tree and reading its documentation, I found a few bits confusing, mainly about the reserved values. So here are some changes hoping to make things clearer.

I am not familiar with the implementation, so I might be getting things wrong, hence this being RFC.

While looking at the code I also found that although the doc claims the normal API blocks reserved value stores, the code checks this using xa_is_advanced(), which only blocks values up to 1026, not up to the max maple tree reserved value 4094. For this part I am not sure whether the code needs to be changed or we can also improve the doc.

Any feedback is appreciated, thanks!

Wei-Lin Chang (2):
Documentation: maple_tree: Point out constraint when using xa_{mk,
to}_value
Documentation: maple_tree: Clarify behavior when using reserved values

 Documentation/core-api/maple_tree.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
Signature · 1 line
2.43.0