From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: "sangjung.woo" <sangjung.woo@samsung.com>,
Alessandro Rubini <rubini@gnudd.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] rtc: pl030: Use devm_kzalloc() instead of kmalloc()
Date: Thu, 10 Oct 2013 16:06:03 -0700 [thread overview]
Message-ID: <20131010160603.1489fe054c2bdc0a0eb9460f@linux-foundation.org> (raw)
In-Reply-To: <1381294767.2040.5.camel@joe-AO722>
On Tue, 08 Oct 2013 21:59:27 -0700 Joe Perches <joe@perches.com> wrote:
> I was a bit surprised to find there isn't a devm_kmalloc.
Yes, the unconditional memset is silly. Especially when the
function has a handy gfp_t and could be passed __GFP_ZERO.
The comment says "managed kzalloc/kfree for device drivers, no kmalloc,
always use kzalloc". There's no explanation for this - it looks like
some ideological thing.
--- a/drivers/base/devres.c~a
+++ a/drivers/base/devres.c
@@ -91,7 +91,8 @@ static __always_inline struct devres * a
if (unlikely(!dr))
return NULL;
- memset(dr, 0, tot_size);
+ if (gfp & __GFP_ZERO)
+ memset(dr, 0, tot_size);
INIT_LIST_HEAD(&dr->node.entry);
dr->node.release = release;
return dr;
@@ -770,7 +771,7 @@ static int devm_kzalloc_match(struct dev
* RETURNS:
* Pointer to allocated memory on success, NULL on failure.
*/
-void * devm_kzalloc(struct device *dev, size_t size, gfp_t gfp)
+static void *__devm_kzalloc(struct device *dev, size_t size, gfp_t gfp)
{
struct devres *dr;
@@ -783,8 +784,19 @@ void * devm_kzalloc(struct device *dev,
devres_add(dev, dr->data);
return dr->data;
}
+
+void *devm_kzalloc(struct device *dev, size_t size, gfp_t gfp)
+{
+ return __devm_kzalloc(dev, size, gfp | __GFP_ZERO);
+}
EXPORT_SYMBOL_GPL(devm_kzalloc);
+void *devm_kmalloc(struct device *dev, size_t size, gfp_t gfp)
+{
+ return __devm_kzalloc(dev, size, gfp);
+}
+EXPORT_SYMBOL_GPL(devm_kmalloc);
+
/**
* devm_kfree - Resource-managed kfree
* @dev: Device this memory belongs to
--- a/include/linux/device.h~a
+++ a/include/linux/device.h
@@ -602,8 +602,9 @@ extern void devres_close_group(struct de
extern void devres_remove_group(struct device *dev, void *id);
extern int devres_release_group(struct device *dev, void *id);
-/* managed kzalloc/kfree for device drivers, no kmalloc, always use kzalloc */
+/* managed kmalloc/kzalloc/kfree for device drivers */
extern void *devm_kzalloc(struct device *dev, size_t size, gfp_t gfp);
+extern void *devm_kmalloc(struct device *dev, size_t size, gfp_t gfp);
extern void devm_kfree(struct device *dev, void *p);
void __iomem *devm_ioremap_resource(struct device *dev, struct resource *res);
_
next prev parent reply other threads:[~2013-10-10 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 4:00 Sangjung Woo
2013-10-09 4:07 ` Joe Perches
2013-10-09 4:36 ` sangjung.woo
2013-10-09 4:59 ` Joe Perches
2013-10-09 5:32 ` sangjung.woo
2013-10-10 23:06 ` Andrew Morton [this message]
2013-10-10 23:14 ` Joe Perches
2013-10-10 23:46 ` Andrew Morton
2013-10-10 23:18 ` Tejun Heo
2013-10-10 23:25 ` 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=20131010160603.1489fe054c2bdc0a0eb9460f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rtc-linux@googlegroups.com \
--cc=rubini@gnudd.com \
--cc=sangjung.woo@samsung.com \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®