linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>, <jiri@resnulli.us>
Cc: <42.hyeyoo@gmail.com>, <akpm@linux-foundation.org>,
	<cl@linux.com>, <danielj@nvidia.com>, <iamjoonsoo.kim@lge.com>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<mingo@kernel.org>, <penberg@kernel.org>, <peterz@infradead.org>,
	<rientjes@google.com>, <roman.gushchin@linux.dev>,
	<vbabka@suse.cz>
Subject: Re: Re [patch RFC] mm/slab: introduce KZALLOC_FREE() cleanup-ed allocation macro
Date: Mon, 25 Mar 2024 12:00:49 -0700	[thread overview]
Message-ID: <6601c9e161df3_2690d294e5@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <20240321162648.23693-1-przemyslaw.kitszel@intel.com>

Przemek Kitszel wrote:
> > From: Jiri Pirko <jiri@nvidia.com>
> > 
> > With introduction of __free() macro using cleanup infrastructure, it
> > will very likely become quite common to see following pattern:
> > 	type *var __free(kfree) = kzalloc(sizeof(*var), GFP_KERNEL);
> > 
> > To follow the CLASS() flow from cleanup.h, introduce a simple macro
> > KZALLOC_FREE() to wrap this over and allow the same flow.
> > 
> > Show an example usage in gpio-sim driver.
> > 
> > Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> > ---
> >  drivers/gpio/gpio-sim.c | 3 +--
> >  include/linux/slab.h    | 3 +++
> >  2 files changed, 4 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpio/gpio-sim.c b/drivers/gpio/gpio-sim.c
> > index c4106e37e6db..997237b3d80c 100644
> > --- a/drivers/gpio/gpio-sim.c
> > +++ b/drivers/gpio/gpio-sim.c
> > @@ -1496,8 +1496,7 @@ gpio_sim_config_make_device_group(struct config_group *group, const char *name)
> >  {
> >  	int id;
> >  
> > -	struct gpio_sim_device *dev __free(kfree) = kzalloc(sizeof(*dev),
> > -							    GFP_KERNEL);
> > +	KZALLOC_FREE(struct gpio_sim_device *, dev, GFP_KERNEL);
> >  	if (!dev)
> >  		return ERR_PTR(-ENOMEM);
> >  
> > diff --git a/include/linux/slab.h b/include/linux/slab.h
> > index b5f5ee8308d0..baee6acd58d3 100644
> > --- a/include/linux/slab.h
> > +++ b/include/linux/slab.h
> > @@ -711,6 +711,9 @@ static inline __alloc_size(1) void *kzalloc(size_t size, gfp_t flags)
> >  	return kmalloc(size, flags | __GFP_ZERO);
> >  }
> >  
> > +#define KZALLOC_FREE(_type, var, _gfp_t)				\
> > +	_type var __free(kfree) = kzalloc(sizeof(*var), _gfp_t)
> > +
> 
> Nice, but I would rather see this wrapper in the cleanup.h file, that have all
> of the rest of related stuff.
> 
> On top of that, I want to propose also a wrapper that is simpler in that it
> does not allocate but just assigns null, with that in mind `_FREE` part of your
> proposed name does not sound right.

No, do not hide assignments within macros

http://lore.kernel.org/r/CAHk-=whYxkfLVtBW_B-PgNqhKOAThTbfoH5CxtOTkwOB6VOt6w@mail.gmail.com

I.e. the amount of incremenal cleverness that include/linux/cleanup.h
will tolerate is low. Any helper should look like typical C.


  reply	other threads:[~2024-03-25 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 13:22 Jiri Pirko
2024-03-15 21:39 ` David Rientjes
2024-03-16 15:41   ` Jiri Pirko
2024-03-21 16:26 ` Re " Przemek Kitszel
2024-03-25 19:00   ` Dan Williams [this message]
2024-03-27  7:23     ` Przemek Kitszel

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=6601c9e161df3_2690d294e5@dwillia2-mobl3.amr.corp.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=danielj@nvidia.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=vbabka@suse.cz \
    /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