From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Liam R. Howlett (Oracle)" <liam@infradead.org>
Cc: Rik van Riel <riel@surriel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
maple-tree@lists.infradead.org
Subject: Re: [PATCH v3 15/19] maple_tree: Document erase and allocations better
Date: Fri, 21 Aug 2026 18:55:58 -0300 [thread overview]
Message-ID: <20260821215558.GA1449020@ziepe.ca> (raw)
In-Reply-To: <ufmfevzbrdg44ovtraidb3xt4ba6uneej6e5rkf5cmkkyp4ubi@3tvzvyj7kh3e>
On Fri, Aug 21, 2026 at 04:37:48PM -0400, Liam R. Howlett (Oracle) wrote:
> On 26/08/21 03:34PM, Rik van Riel wrote:
> > On Fri, 2026-08-21 at 15:26 -0400, Liam R. Howlett (Oracle) wrote:
> > >
> > > knowing one value within that range, or mtree_store() call with an
> > > entry of
> > > -NULL may be used to partially erase a range or many ranges at once.
> > > +NULL may be used to partially erase a range or many ranges at once.
> > > Note that
> > > +mtree_erase() may use GFP_KERNEL | __GFP_NOFAIL for allocations and
> > > cannot
> > > +fail, but may need to sleep - do not use mtree_erase() from a
> > > blocking context.
> > >
> >
> > Do you mean "from a context that cannot block" ?
>
> Ah, that's not clear.
>
> "Do not use mtree_erase() from a context that cannot tolerate blocking"
>
> Is that better?
I would say 'can sleep, so must not be called from an atomic context' ?
If that is what you mean..
Jason
next prev parent reply other threads:[~2026-08-21 21:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 19:26 [PATCH v3 00/19] maple_tree: lock checking and clean ups Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 01/19] maple_tree: Add rcu locking check when LOCKDEP is enabled Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 02/19] locking/lockdep: Add sequence counter to held_lock Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 03/19] maple_tree: Add write lock checking with lockdep sequence numbers Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 04/19] maple_tree: Documentation fix Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 05/19] maple_tree: Drop dead code from mas_extend_spanning_null() Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 06/19] maple_tree: Drop MAPLE_ALLOC_SLOTS Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 07/19] maple_tree: Clarify comments on mas_nomem() Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 08/19] maple_tree: Use prefetched value in mas_wr_store_type() Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 09/19] maple_tree: Optimise mas_wr_node_store() when not in rcu mode Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 10/19] maple_tree: micro optimisation of mas_wr_store_type() Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 11/19] maple_tree: Add bulk parent set helper Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 12/19] maple_tree: Catch race in mas_alloc_cyclic() Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 13/19] maple_tree: Document that erase may use GFP_KERNEL for allocations Liam R. Howlett (Oracle)
2026-08-21 19:33 ` Rik van Riel
2026-08-21 19:26 ` [PATCH v3 14/19] maple_tree: Avoid mas_erase() and mtree_erase() failures Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 15/19] maple_tree: Document erase and allocations better Liam R. Howlett (Oracle)
2026-08-21 19:34 ` Rik van Riel
2026-08-21 20:37 ` Liam R. Howlett (Oracle)
2026-08-21 21:55 ` Jason Gunthorpe [this message]
2026-08-21 19:26 ` [PATCH v3 16/19] maple_tree: Change two GFP flags in tests Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 17/19] maple_tree: Fix argument name in header Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 18/19] maple_tree: Avoid extra gap calculation Liam R. Howlett (Oracle)
2026-08-21 19:26 ` [PATCH v3 19/19] maple_tree: Add helper mas_make_walkable() Liam R. Howlett (Oracle)
2026-08-21 19:40 ` [PATCH v3 00/19] maple_tree: lock checking and clean ups Liam R. Howlett (Oracle)
2026-08-21 22:42 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260821215558.GA1449020@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=riel@surriel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox