From: Andrzej Hajda <a.hajda@samsung.com>
To: linux-mm@kvack.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/4] kstrdup optimization
Date: Wed, 31 Dec 2014 14:05:12 +0100 [thread overview]
Message-ID: <54A3F488.8060904@samsung.com> (raw)
In-Reply-To: <1419864510-24834-1-git-send-email-a.hajda@samsung.com>
On 12/29/2014 03:48 PM, Andrzej Hajda wrote:
(...)
> As I have tested it on mobile platform (exynos4210-trats) it saves above 2600
> string duplications. Below simple stats about the most frequent duplications:
> Count String
> 880 power
> 874 subsystem
> 130 device
> 126 parameters
> 61 iommu_group
> 40 driver
> 28 bdi
> 28 none
> 25 sclk_mpll
> 23 sclk_usbphy0
> 23 sclk_hdmi24m
> 23 xusbxti
> 22 sclk_vpll
> 22 sclk_epll
> 22 xxti
> 20 sclk_hdmiphy
> 11 aclk100
Minor update, printk buffer was too short during tests so I have not
catched everything. In fact the patchset saves 3260 duplications. Below
stats per kstrdup_const caller:
2260 __kernfs_new_node+0x28/0xc4
631 clk_register+0xc8/0x1b8
318 clk_register+0x34/0x1b8
51 kmem_cache_create+0x7c/0x1c8
Regards
Andrzej
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Andrzej Hajda <a.hajda@samsung.com>
To: linux-mm@kvack.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/4] kstrdup optimization
Date: Wed, 31 Dec 2014 14:05:12 +0100 [thread overview]
Message-ID: <54A3F488.8060904@samsung.com> (raw)
In-Reply-To: <1419864510-24834-1-git-send-email-a.hajda@samsung.com>
On 12/29/2014 03:48 PM, Andrzej Hajda wrote:
(...)
> As I have tested it on mobile platform (exynos4210-trats) it saves above 2600
> string duplications. Below simple stats about the most frequent duplications:
> Count String
> 880 power
> 874 subsystem
> 130 device
> 126 parameters
> 61 iommu_group
> 40 driver
> 28 bdi
> 28 none
> 25 sclk_mpll
> 23 sclk_usbphy0
> 23 sclk_hdmi24m
> 23 xusbxti
> 22 sclk_vpll
> 22 sclk_epll
> 22 xxti
> 20 sclk_hdmiphy
> 11 aclk100
Minor update, printk buffer was too short during tests so I have not
catched everything. In fact the patchset saves 3260 duplications. Below
stats per kstrdup_const caller:
2260 __kernfs_new_node+0x28/0xc4
631 clk_register+0xc8/0x1b8
318 clk_register+0x34/0x1b8
51 kmem_cache_create+0x7c/0x1c8
Regards
Andrzej
next prev parent reply other threads:[~2014-12-31 13:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 14:48 [RFC PATCH 0/4] kstrdup optimization Andrzej Hajda
2014-12-29 14:48 ` Andrzej Hajda
2014-12-29 14:48 ` [RFC PATCH 1/4] mm/util: add kstrdup_const Andrzej Hajda
2014-12-29 14:48 ` Andrzej Hajda
2014-12-29 14:48 ` [RFC PATCH 2/4] kernfs: use kstrdup_const for node name allocation Andrzej Hajda
2014-12-29 14:48 ` Andrzej Hajda
2014-12-29 14:48 ` [RFC PATCH 3/4] clk: use kstrdup_const for clock name allocations Andrzej Hajda
2014-12-29 14:48 ` Andrzej Hajda
2014-12-29 14:48 ` [RFC PATCH 4/4] mm/slab: use kstrdup_const for allocating cache names Andrzej Hajda
2014-12-29 14:48 ` Andrzej Hajda
2014-12-30 6:45 ` [RFC PATCH 0/4] kstrdup optimization Andi Kleen
2014-12-30 6:45 ` Andi Kleen
2014-12-30 7:16 ` Andrzej Hajda
2014-12-30 7:16 ` Andrzej Hajda
2014-12-30 8:32 ` Andreas Mohr
2014-12-30 8:32 ` Andreas Mohr
2014-12-30 21:29 ` Andi Kleen
2014-12-30 21:29 ` Andi Kleen
2015-01-08 10:54 ` Andrzej Hajda
2015-01-08 10:54 ` Andrzej Hajda
2014-12-31 13:05 ` Andrzej Hajda [this message]
2014-12-31 13:05 ` Andrzej Hajda
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=54A3F488.8060904@samsung.com \
--to=a.hajda@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.