From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
David Laight <david.laight.linux@gmail.com>,
Li Nan <linan122@huawei.com>, Mike Rapoport <rppt@kernel.org>,
Song Liu <song@kernel.org>, Xiao Ni <xiao@kernel.org>,
Yu Kuai <yukuai@fnnas.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-raid@vger.kernel.org
Subject: [PATCH v3 0/2] lib/raid: replace __get_free_pages() call with kvmalloc()
Date: Thu, 28 May 2026 10:27:54 +0300 [thread overview]
Message-ID: <20260528-lib-v3-0-feccddf1cb6d@kernel.org> (raw)
This is a (tiny) part of larger work of replacing page allocator calls
with k*malloc.
Nowadays the right way to say "I need a buffer" is kmalloc() rather than
ancient and ugly __get_free_pages().
---
v3 changes:
* restore kmalloc() per Christoph
* update changelog
v2: https://patch.msgid.link/20260526-lib-v2-0-ca3f0fc24b14@kernel.org
* replace kmalloc() with kvmalloc()
v1: https://patch.msgid.link/20260520-lib-v1-0-cb3045bef2d8@kernel.org
---
Mike Rapoport (Microsoft) (2):
xor: use kmalloc() in calibrate_xor_blocks()
raid6: use kmalloc() in raid6_select_algo()
lib/raid/xor/xor-core.c | 5 +++--
lib/raid6/algos.c | 6 +++---
2 files changed, 6 insertions(+), 5 deletions(-)
---
base-commit: 5d6919055dec134de3c40167a490f33c74c12581
change-id: 20260520-lib-8afb92134307
Best regards,
--
Sincerely yours,
Mike.
next reply other threads:[~2026-05-28 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 7:27 Mike Rapoport (Microsoft) [this message]
2026-05-28 7:27 ` [PATCH v3 1/2] xor: use kmalloc() in calibrate_xor_blocks() Mike Rapoport (Microsoft)
2026-05-28 8:54 ` Christoph Hellwig
2026-05-28 9:49 ` Mike Rapoport
2026-05-28 7:27 ` [PATCH v3 2/2] raid6: use kmalloc() in raid6_select_algo() Mike Rapoport (Microsoft)
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=20260528-lib-v3-0-feccddf1cb6d@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david.laight.linux@gmail.com \
--cc=hch@infradead.org \
--cc=linan122@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=xiao@kernel.org \
--cc=yukuai@fnnas.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