From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Harry Yoo <harry.yoo@oracle.com>,
Uladzislau Rezki <urezki@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, maple-tree@lists.infradead.org
Subject: Re: [PATCH v5 06/14] tools: Add sheaves support to testing infrastructure
Date: Tue, 26 Aug 2025 11:59:42 +0200 [thread overview]
Message-ID: <95413138-1a9c-4b10-847d-cb37b68ba7c4@suse.cz> (raw)
In-Reply-To: <CAJuCfpEsVE7Jae7PqWvgTtm38C5MPFx43+dDyYzfKLMQFuE_3A@mail.gmail.com>
On 8/22/25 18:56, Suren Baghdasaryan wrote:
>> @@ -270,6 +276,84 @@ __kmem_cache_create_args(const char *name, unsigned int size,
>> return ret;
>> }
>>
>> +struct slab_sheaf *
>> +kmem_cache_prefill_sheaf(struct kmem_cache *s, gfp_t gfp, unsigned int size)
>> +{
>> + struct slab_sheaf *sheaf;
>> + unsigned int capacity;
>> +
>> + if (size > s->sheaf_capacity)
>> + capacity = size;
>> + else
>> + capacity = s->sheaf_capacity;
>
> nit:
> capacity = max(size, s->sheaf_capacity);
OK
>> +
>> + sheaf = malloc(sizeof(*sheaf) + sizeof(void *) * s->sheaf_capacity * capacity);
>
> Should this really be `sizeof(void *) * s->sheaf_capacity * capacity`
> or just `sizeof(void *) * capacity` ?
Right, so the whole thing should be:
sizeof(*sheaf) + sizeof(void *) * capacity
>
>> + if (!sheaf) {
>> + return NULL;
>> + }
>> +
>> + memset(sheaf, 0, size);
This is also wrong, so I'm changing it to calloc(1, ...) to get the zeroing
there.
>> + sheaf->cache = s;
>> + sheaf->capacity = capacity;
>> + sheaf->size = kmem_cache_alloc_bulk(s, gfp, size, sheaf->objects);
>> + if (!sheaf->size) {
>> + free(sheaf);
>> + return NULL;
>> + }
>> +
>> + return sheaf;
>> +}
>> +
>> +int kmem_cache_refill_sheaf(struct kmem_cache *s, gfp_t gfp,
>> + struct slab_sheaf **sheafp, unsigned int size)
>> +{
>> + struct slab_sheaf *sheaf = *sheafp;
>> + int refill;
>> +
>> + if (sheaf->size >= size)
>> + return 0;
>> +
>> + if (size > sheaf->capacity) {
>> + sheaf = kmem_cache_prefill_sheaf(s, gfp, size);
>> + if (!sheaf)
>> + return -ENOMEM;
>> +
>> + kmem_cache_return_sheaf(s, gfp, *sheafp);
>> + *sheafp = sheaf;
>> + return 0;
>> + }
>> +
>> + refill = kmem_cache_alloc_bulk(s, gfp, size - sheaf->size,
>> + &sheaf->objects[sheaf->size]);
>> + if (!refill)
>> + return -ENOMEM;
>> +
>> + sheaf->size += refill;
>> + return 0;
>> +}
>> +
>> +void kmem_cache_return_sheaf(struct kmem_cache *s, gfp_t gfp,
>> + struct slab_sheaf *sheaf)
>> +{
>> + if (sheaf->size) {
>> + //s->non_kernel += sheaf->size;
>
> Above comment seems obsolete.
Ack.
>
>> + kmem_cache_free_bulk(s, sheaf->size, &sheaf->objects[0]);
>> + }
>> + free(sheaf);
>> +}
>> +
>> +void *
>> +kmem_cache_alloc_from_sheaf(struct kmem_cache *s, gfp_t gfp,
>> + struct slab_sheaf *sheaf)
>> +{
>> + if (sheaf->size == 0) {
>> + printf("Nothing left in sheaf!\n");
>> + return NULL;
>> + }
>> +
>
> Should we clear sheaf->objects[sheaf->size] for additional safety?
OK.
>> + return sheaf->objects[--sheaf->size];
>> +}
>> +
>> /*
>> * Test the test infrastructure for kem_cache_alloc/free and bulk counterparts.
>> */
>>
>> --
>> 2.50.1
>>
next prev parent reply other threads:[~2025-08-26 9:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 13:34 [PATCH v5 00/14] SLUB percpu sheaves Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 01/14] slab: add opt-in caching layer of " Vlastimil Babka
2025-08-18 10:09 ` Harry Yoo
2025-08-26 8:03 ` Vlastimil Babka
2025-08-19 4:19 ` Suren Baghdasaryan
2025-08-26 8:51 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 02/14] slab: add sheaf support for batching kfree_rcu() operations Vlastimil Babka
2025-07-23 16:39 ` Uladzislau Rezki
2025-07-24 14:30 ` Vlastimil Babka
2025-07-24 17:36 ` Uladzislau Rezki
2025-07-23 13:34 ` [PATCH v5 03/14] slab: sheaf prefilling for guaranteed allocations Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 04/14] slab: determine barn status racily outside of lock Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 05/14] tools: Add testing support for changes to rcu and slab for sheaves Vlastimil Babka
2025-08-22 16:28 ` Suren Baghdasaryan
2025-08-26 9:32 ` Vlastimil Babka
2025-08-27 0:19 ` Suren Baghdasaryan
2025-07-23 13:34 ` [PATCH v5 06/14] tools: Add sheaves support to testing infrastructure Vlastimil Babka
2025-08-22 16:56 ` Suren Baghdasaryan
2025-08-26 9:59 ` Vlastimil Babka [this message]
2025-07-23 13:34 ` [PATCH v5 07/14] maple_tree: use percpu sheaves for maple_node_cache Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 08/14] mm, vma: use percpu sheaves for vm_area_struct cache Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 09/14] mm, slub: skip percpu sheaves for remote object freeing Vlastimil Babka
2025-08-25 5:22 ` Harry Yoo
2025-08-26 10:11 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 10/14] mm, slab: allow NUMA restricted allocations to use percpu sheaves Vlastimil Babka
2025-08-22 19:58 ` Suren Baghdasaryan
2025-08-25 6:52 ` Harry Yoo
2025-08-26 10:49 ` Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 11/14] testing/radix-tree/maple: Increase readers and reduce delay for faster machines Vlastimil Babka
2025-07-23 13:34 ` [PATCH v5 12/14] maple_tree: Sheaf conversion Vlastimil Babka
2025-08-22 20:18 ` Suren Baghdasaryan
2025-08-26 14:22 ` Liam R. Howlett
2025-08-27 2:07 ` Suren Baghdasaryan
2025-08-28 14:27 ` Liam R. Howlett
2025-07-23 13:34 ` [PATCH v5 13/14] maple_tree: Add single node allocation support to maple state Vlastimil Babka
2025-08-22 20:25 ` Suren Baghdasaryan
2025-08-26 15:10 ` Liam R. Howlett
2025-08-27 2:03 ` Suren Baghdasaryan
2025-07-23 13:34 ` [PATCH v5 14/14] maple_tree: Convert forking to use the sheaf interface Vlastimil Babka
2025-08-22 20:29 ` Suren Baghdasaryan
2025-08-15 22:53 ` [PATCH v5 00/14] SLUB percpu sheaves Sudarsan Mahendran
2025-08-16 8:05 ` Harry Yoo
2025-08-16 17:35 ` Sudarsan Mahendran
2025-08-16 18:31 ` Vlastimil Babka
2025-08-16 18:33 ` Vlastimil Babka
2025-08-17 4:28 ` Sudarsan Mahendran
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=95413138-1a9c-4b10-847d-cb37b68ba7c4@suse.cz \
--to=vbabka@suse.cz \
--cc=Liam.Howlett@oracle.com \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=surenb@google.com \
--cc=urezki@gmail.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;
as well as URLs for NNTP newsgroup(s).