From: Matthew Wilcox <willy@infradead.org>
To: linux-mm@kvack.org
Subject: [PROJECT IDEA] More kmalloc sizes
Date: Fri, 25 Oct 2019 07:51:25 -0700 [thread overview]
Message-ID: <20191025145125.GO2963@bombadil.infradead.org> (raw)
I was thinking about doing something which would require allocating 1024
bytes plus an 8 byte header. It occurred to me this is practically the
worst possible case for our current slab allocator -- it will round the
1032 byte allocation up to 2048 and we'll get two of them per page.
If we had a slab that was 1344 bytes, we could get three objects like
this per page, and they'd still be 64 byte aligned. Similarly, it might
be worth adding slabs of size 576 (512 + header, get 7 per page) and 320
(256 + header, get 12 per page). Should be a fairly simple project for
someone to undertake.
reply other threads:[~2019-10-25 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191025145125.GO2963@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-mm@kvack.org \
/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