From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Mark Brown <broonie@kernel.org>, Matthew Wilcox <willy@infradead.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, ksummit@lists.linux.dev
Subject: Re: [TECH TOPIC] Implementing malloc
Date: Mon, 29 Jun 2026 20:37:19 +0200 [thread overview]
Message-ID: <abdedc4d-2067-4b8a-8bd0-276f421cd4a9@kernel.org> (raw)
In-Reply-To: <32f6b38a-043b-4f51-aec7-aefcc7d0cc13@sirena.org.uk>
On 6/29/26 8:29 PM, Mark Brown wrote:
> On Mon, Jun 29, 2026 at 07:19:20PM +0100, Matthew Wilcox wrote:
>
>> But we do have code which just needs to allocate "some memory", doesn't
>> have any particularly weird restrictions, and where usability is more
>> important than "pedal to the metal". An example might be something
>> like zlib. It needs to allocate some temporary memory, and why have to
>
> Or drivers just allocating some driver data. TBH kzalloc() kind of ends
> up being that function a lot of the time, I'm not convinced that a high
> proportion of the kzalloc(x, GFP_KERNEL) calls out there are the result
> of a deep consideration of which allocator to use.
Actually "x = kzalloc_obj(*x);" these days, with the GFP_KERNEL implicit.
next prev parent reply other threads:[~2026-06-29 18:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 14:29 [TECH TOPIC] Implementing malloc Matthew Wilcox
2026-06-29 15:07 ` Dan Carpenter
2026-06-29 15:21 ` H. Peter Anvin
2026-06-29 15:31 ` Matthew Wilcox
2026-06-29 16:00 ` Vlastimil Babka (SUSE)
2026-06-29 16:37 ` H. Peter Anvin
2026-06-29 16:48 ` Alexey Dobriyan
2026-06-29 16:48 ` H. Peter Anvin
2026-06-29 18:19 ` Matthew Wilcox
2026-06-29 18:22 ` H. Peter Anvin
2026-06-29 18:29 ` Mark Brown
2026-06-29 18:37 ` Vlastimil Babka (SUSE) [this message]
2026-06-30 18:53 ` Steven Rostedt
2026-07-09 16:58 ` Kees Cook
2026-07-09 17:11 ` Matthew Wilcox
2026-07-09 17:30 ` H. Peter Anvin
2026-07-09 17:39 ` Greg KH
2026-07-09 17:42 ` Miguel Ojeda
2026-07-09 17:40 ` Miguel Ojeda
2026-07-09 18:18 ` H. Peter Anvin
2026-07-09 18:44 ` Miguel Ojeda
2026-07-09 18:50 ` H. Peter Anvin
2026-07-09 19:04 ` Miguel Ojeda
2026-07-09 18:42 ` Dan Carpenter
2026-07-09 18:45 ` Matthew Wilcox
2026-07-09 19:13 ` Linus Torvalds
2026-07-10 11:21 ` Geert Uytterhoeven
2026-07-10 11:44 ` Laurent Pinchart
2026-07-10 12:16 ` Joe Perches
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=abdedc4d-2067-4b8a-8bd0-276f421cd4a9@kernel.org \
--to=vbabka@kernel.org \
--cc=broonie@kernel.org \
--cc=hpa@zytor.com \
--cc=ksummit@lists.linux.dev \
--cc=willy@infradead.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