From: Danilo Krummrich <dakr@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Vlastimil Babka <vbabka@suse.cz>,
"Liam R. Howlett" <Liam.Howlett@Oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
maple-tree@lists.infradead.org
Subject: Re: [PATCH] maple_tree: export symbol mas_preallocate()
Date: Wed, 8 Mar 2023 16:18:55 +0100 [thread overview]
Message-ID: <59b703ac-9660-a0e5-09f7-c5b69d4f39cb@redhat.com> (raw)
In-Reply-To: <20230308144343.GA16259@lst.de>
On 3/8/23 15:43, Christoph Hellwig wrote:
> On Wed, Mar 08, 2023 at 03:34:29PM +0100, Danilo Krummrich wrote:
>> On 3/8/23 11:59, Vlastimil Babka wrote:
>>> On 3/2/23 02:52, Liam R. Howlett wrote:
>>>> Thanks for the patch. This should indeed be exported.
>>>>
>>>> Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
>>>
>>> What uses it? Don't we export only things used by in-kernel modules?
>>
>> mas_preallocate() is part of the maple tree's 'Advanced API'. All other
>> functions of this API are exported already.
>>
>> More specifically, e.g. mas_store_prealloc() is exported which doesn't make
>> a lot of sense without mas_preallocate() being available too.
>>
>> I don't think it is used outside of mm yet, but as a generic tree
>> implementation maple tree is pretty likely to be used in code built as
>> module, e.g. drivers.
>
> If anyone wants to use they can add the export as needed.
>
Valid perception, though personally I wouldn't share it in this specific
case.
Anyway, it's just that all other functions of the 'Advanced API' are
exported already without them having other users than mm either, e.g.
mas_store_prealloc() can't be used without mas_preallocate(), hence
exporting one, but not the other doesn't really make sense.
Consistency wise I think we should either also export mas_preallocate()
or don't export the other ones either.
next prev parent reply other threads:[~2023-03-08 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 1:10 Danilo Krummrich
2023-03-02 1:52 ` Liam R. Howlett
2023-03-08 10:59 ` Vlastimil Babka
2023-03-08 14:34 ` Danilo Krummrich
2023-03-08 14:43 ` Christoph Hellwig
2023-03-08 15:18 ` Danilo Krummrich [this message]
2023-03-08 15:29 ` Christoph Hellwig
2023-03-08 17:43 ` Matthew Wilcox
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=59b703ac-9660-a0e5-09f7-c5b69d4f39cb@redhat.com \
--to=dakr@redhat.com \
--cc=Liam.Howlett@Oracle.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=vbabka@suse.cz \
/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