[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZCHKO93L5MD7NWZq@casper.infradead.org>
Date: Mon, 27 Mar 2023 17:54:19 +0100
From: Matthew Wilcox <willy@...radead.org>
To: "Uladzislau Rezki (Sony)" <urezki@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>, Baoquan He <bhe@...hat.com>,
Lorenzo Stoakes <lstoakes@...il.com>,
Christoph Hellwig <hch@...radead.org>,
Dave Chinner <david@...morbit.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>
Subject: Re: [PATCH v2 1/2] mm: vmalloc: Remove a global vmap_blocks xarray
On Mon, Mar 27, 2023 at 06:52:26PM +0200, Uladzislau Rezki (Sony) wrote:
> @@ -1927,25 +1940,47 @@ struct vmap_block {
> /* Queue of free and dirty vmap blocks, for allocation and flushing purposes */
> static DEFINE_PER_CPU(struct vmap_block_queue, vmap_block_queue);
>
> -/*
> - * XArray of vmap blocks, indexed by address, to quickly find a vmap block
> - * in the free path. Could get rid of this if we change the API to return a
> - * "cookie" from alloc, to be passed to free. But no big deal yet.
> +/**
This is marked for kernel-doc without being in kernel-doc format.
I'd suggest just using a single '*'.
Powered by blists - more mailing lists