From: Andrew Morton <akpm@linux-foundation.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Caleb Sander Mateos <csander@purestorage.com>,
Uday Shankar <ushankar@purestorage.com>,
Stefani Seibold <stefani@seibold.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 01/27] kfifo: add kfifo_alloc_node() helper for NUMA awareness
Date: Thu, 13 Nov 2025 14:06:20 -0800 [thread overview]
Message-ID: <20251113140620.bc768aa94d734a654c31857c@linux-foundation.org> (raw)
In-Reply-To: <aRUypQzcovGikrV0@fedora>
On Thu, 13 Nov 2025 09:21:41 +0800 Ming Lei <ming.lei@redhat.com> wrote:
> > > +#define kfifo_alloc_node(fifo, size, gfp_mask, node) \
> > > +__kfifo_int_must_check_helper( \
> > > +({ \
> > > + typeof((fifo) + 1) __tmp = (fifo); \
> > > + struct __kfifo *__kfifo = &__tmp->kfifo; \
> > > + __is_kfifo_ptr(__tmp) ? \
> > > + __kfifo_alloc_node(__kfifo, size, sizeof(*__tmp->type), gfp_mask, node) : \
> > > + -EINVAL; \
> > > +}) \
> > > +)
> >
> > Well this is an eyesore. Do we really need it? It seems to be here so
> > we can check for a programming bug? Well, don't add programming bugs!
> >
> > I'm actually not enjoying the existence of __is_kfifo_ptr() at all.
> > What is it all doing? It's a FIFO for heck's sake, why is this so hard.
>
> It is basically a clone of existing kfifo_alloc().
>
> Do we need to clean kfifo_alloc() first? Otherwise I'd keep the same
> pattern with existing definitions.
Is OK, I was just whining. Possibly de-over-engineering kifo is a
separate project.
next prev parent reply other threads:[~2025-11-13 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251112093808.2134129-1-ming.lei@redhat.com>
2025-11-12 9:37 ` [PATCH V3 01/27] kfifo: add kfifo_alloc_node() helper for NUMA awareness Ming Lei
2025-11-12 19:29 ` Andrew Morton
2025-11-13 1:21 ` Ming Lei
2025-11-13 22:06 ` Andrew Morton [this message]
2025-11-15 4:14 ` Caleb Sander Mateos
2025-11-16 11:59 ` Ming Lei
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=20251113140620.bc768aa94d734a654c31857c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=stefani@seibold.net \
--cc=ushankar@purestorage.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