From: Philipp Stanner <phasta@mailbox.org>
To: Qianfeng Rong <rongqianfeng@vivo.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Philipp Stanner <phasta@kernel.org>,
Thorsten Blum <thorsten.blum@linux.dev>,
"open list:SOUND" <linux-sound@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] ALSA: use vmalloc_array() to simplify code
Date: Mon, 25 Aug 2025 13:50:40 +0200 [thread overview]
Message-ID: <0f0cef136230d97e9181cd2e61a365d1ceb00cb7.camel@mailbox.org> (raw)
In-Reply-To: <f1e66db3-980c-4e06-98cc-021c166e9b21@vivo.com>
On Mon, 2025-08-25 at 19:46 +0800, Qianfeng Rong wrote:
>
> 在 2025/8/25 19:01, Andy Shevchenko 写道:
> > On Sun, Aug 24, 2025 at 09:55:09PM +0800, Qianfeng Rong wrote:
> > > Remove array_size() calls and replace vmalloc() with vmalloc_array() to
> > > simplify the code and maintain consistency with existing kmalloc_array()
> > > usage.
> > >
> > > vmalloc_array() is also optimized better, resulting in less instructions
> > > being used [1].
> > Have you considered using sizeof(*...) where it makes sense?
> I believe that sizeof(*...) should preferably not be mixed with this patch;
> instead, it should be addressed in a separate, independent patch that
> covers all relevant instances.
>
> Additionally, I understand that not everyone prefers using sizeof(*...), as
> it reduces readability. What do you think, Andy?
I agree that should be addressed in a separate patch, if at all.
As for sizeof(*foo), one gets used to it. I think it's preferred in the
kernel often because it's more difficult to introduce bugs like so:
long *foo;
foo = kmalloc(sizeof(long) * 9001);
When you later change long *foo to int *foo and forget about the malloc
place, you'll get an overflow.
foo = kmalloc(sizeof(*foo) …) can never have that problem.
Regards
P.
>
> Best regards,
> Qianfeng
> >
prev parent reply other threads:[~2025-08-25 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 13:55 [PATCH 0/3] ALSA: use vmalloc_array() to simplify code Qianfeng Rong
2025-08-24 13:55 ` [PATCH 1/3] ALSA: cs46xx: " Qianfeng Rong
2025-08-24 13:55 ` [PATCH 2/3] ALSA: emu10k1: " Qianfeng Rong
2025-08-24 13:55 ` [PATCH 3/3] ALSA: maestro3: " Qianfeng Rong
2025-08-25 11:01 ` [PATCH 0/3] ALSA: " Andy Shevchenko
2025-08-25 11:46 ` Qianfeng Rong
2025-08-25 11:50 ` Philipp Stanner [this message]
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=0f0cef136230d97e9181cd2e61a365d1ceb00cb7.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phasta@kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=thorsten.blum@linux.dev \
--cc=tiwai@suse.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).