From: Nitin Gupta <ngupta@vflare.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/6] zsmalloc: remove unnecessary alignment
Date: Thu, 03 May 2012 01:16:10 -0400 [thread overview]
Message-ID: <4FA2149A.9030803@vflare.org> (raw)
In-Reply-To: <4F98A818.1080106@kernel.org>
Hi Minchan,
Sorry for late reply.
On 4/25/12 9:42 PM, Minchan Kim wrote:
> On 04/25/2012 09:53 PM, Nitin Gupta wrote:
>
>> On 04/25/2012 02:23 AM, Minchan Kim wrote:
>>
>>> It isn't necessary to align pool size with PAGE_SIZE.
>>> If I missed something, please let me know it.
>>>
>>> Signed-off-by: Minchan Kim<minchan@kernel.org>
>>> ---
>>> drivers/staging/zsmalloc/zsmalloc-main.c | 5 ++---
>>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
>>> index 504b6c2..b99ad9e 100644
>>> --- a/drivers/staging/zsmalloc/zsmalloc-main.c
>>> +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
>>> @@ -489,14 +489,13 @@ fail:
>>>
>>> struct zs_pool *zs_create_pool(const char *name, gfp_t flags)
>>> {
>>> - int i, error, ovhd_size;
>>> + int i, error;
>>> struct zs_pool *pool;
>>>
>>> if (!name)
>>> return NULL;
>>>
>>> - ovhd_size = roundup(sizeof(*pool), PAGE_SIZE);
>>> - pool = kzalloc(ovhd_size, GFP_KERNEL);
>>> + pool = kzalloc(sizeof(*pool), GFP_KERNEL);
>>> if (!pool)
>>> return NULL;
>>>
>>
>>
>> pool metadata is rounded-up to avoid potential false-sharing problem
>> (though we could just roundup to cache_line_size()).
>
>
> Do you really have any hurt by false-sharing problem?
> If so, we can change it with
>
I've never been hit by this false-sharing in any testing but this is
really just a random chance. Apart from aligning to cache-line size,
there is no way to ensure some unfortunate read-mostly object never
falls in the same line.
> kzalloc(ALIGN(sizeof(*pool), cache_line_size()), GFP_KERNEL);
>
Yes, looks better than aligning to PAGE_SIZE.
Thanks,
Nitin
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Nitin Gupta <ngupta@vflare.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/6] zsmalloc: remove unnecessary alignment
Date: Thu, 03 May 2012 01:16:10 -0400 [thread overview]
Message-ID: <4FA2149A.9030803@vflare.org> (raw)
In-Reply-To: <4F98A818.1080106@kernel.org>
Hi Minchan,
Sorry for late reply.
On 4/25/12 9:42 PM, Minchan Kim wrote:
> On 04/25/2012 09:53 PM, Nitin Gupta wrote:
>
>> On 04/25/2012 02:23 AM, Minchan Kim wrote:
>>
>>> It isn't necessary to align pool size with PAGE_SIZE.
>>> If I missed something, please let me know it.
>>>
>>> Signed-off-by: Minchan Kim<minchan@kernel.org>
>>> ---
>>> drivers/staging/zsmalloc/zsmalloc-main.c | 5 ++---
>>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
>>> index 504b6c2..b99ad9e 100644
>>> --- a/drivers/staging/zsmalloc/zsmalloc-main.c
>>> +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
>>> @@ -489,14 +489,13 @@ fail:
>>>
>>> struct zs_pool *zs_create_pool(const char *name, gfp_t flags)
>>> {
>>> - int i, error, ovhd_size;
>>> + int i, error;
>>> struct zs_pool *pool;
>>>
>>> if (!name)
>>> return NULL;
>>>
>>> - ovhd_size = roundup(sizeof(*pool), PAGE_SIZE);
>>> - pool = kzalloc(ovhd_size, GFP_KERNEL);
>>> + pool = kzalloc(sizeof(*pool), GFP_KERNEL);
>>> if (!pool)
>>> return NULL;
>>>
>>
>>
>> pool metadata is rounded-up to avoid potential false-sharing problem
>> (though we could just roundup to cache_line_size()).
>
>
> Do you really have any hurt by false-sharing problem?
> If so, we can change it with
>
I've never been hit by this false-sharing in any testing but this is
really just a random chance. Apart from aligning to cache-line size,
there is no way to ensure some unfortunate read-mostly object never
falls in the same line.
> kzalloc(ALIGN(sizeof(*pool), cache_line_size()), GFP_KERNEL);
>
Yes, looks better than aligning to PAGE_SIZE.
Thanks,
Nitin
next prev parent reply other threads:[~2012-05-03 5:16 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 6:23 [PATCH 0/6] zsmalloc: clean up and fix arch dependency Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 1/6] zsmalloc: use PageFlag macro instead of [set|test]_bit Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 12:43 ` Nitin Gupta
2012-04-25 12:43 ` Nitin Gupta
2012-04-25 6:23 ` [PATCH 2/6] zsmalloc: remove unnecessary alignment Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 12:53 ` Nitin Gupta
2012-04-25 12:53 ` Nitin Gupta
2012-04-26 1:42 ` Minchan Kim
2012-04-26 1:42 ` Minchan Kim
2012-05-03 5:16 ` Nitin Gupta [this message]
2012-05-03 5:16 ` Nitin Gupta
2012-04-25 6:23 ` [PATCH 3/6] zsmalloc: rename zspage_order with zspage_pages Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 13:03 ` Nitin Gupta
2012-04-25 13:03 ` Nitin Gupta
2012-04-26 1:46 ` Minchan Kim
2012-04-26 1:46 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 4/6] zsmalloc: add/fix function comment Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 13:27 ` Nitin Gupta
2012-04-25 13:27 ` Nitin Gupta
2012-04-26 1:51 ` Minchan Kim
2012-04-26 1:51 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 5/6] zsmalloc: remove unnecessary type casting Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 13:35 ` Nitin Gupta
2012-04-25 13:35 ` Nitin Gupta
2012-04-25 17:56 ` Greg Kroah-Hartman
2012-04-25 17:56 ` Greg Kroah-Hartman
2012-04-25 18:13 ` Nitin Gupta
2012-04-25 18:13 ` Nitin Gupta
2012-04-26 1:58 ` Minchan Kim
2012-04-26 1:58 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 6/6] zsmalloc: make zsmalloc portable Minchan Kim
2012-04-25 6:23 ` Minchan Kim
2012-04-25 14:32 ` Nitin Gupta
2012-04-25 14:32 ` Nitin Gupta
2012-04-25 15:40 ` Dan Magenheimer
2012-04-25 15:40 ` Dan Magenheimer
2012-04-26 2:03 ` Minchan Kim
2012-04-26 2:03 ` Minchan Kim
2012-04-26 5:07 ` Minchan Kim
2012-04-26 5:07 ` Minchan Kim
2012-04-30 16:24 ` Seth Jennings
2012-04-30 16:24 ` Seth Jennings
2012-04-25 16:37 ` Seth Jennings
2012-04-25 16:37 ` Seth Jennings
2012-04-26 2:04 ` Minchan Kim
2012-04-26 2:04 ` Minchan Kim
2012-05-07 15:14 ` Seth Jennings
2012-05-07 15:14 ` Seth Jennings
2012-05-08 0:46 ` Minchan Kim
2012-05-08 0:46 ` Minchan Kim
2012-04-26 2:11 ` Minchan Kim
2012-04-26 2:11 ` Minchan Kim
2012-04-25 12:41 ` [PATCH 0/6] zsmalloc: clean up and fix arch dependency Nitin Gupta
2012-04-25 12:41 ` Nitin Gupta
2012-04-26 1:20 ` Minchan Kim
2012-04-26 1:20 ` Minchan Kim
2012-04-25 18:14 ` Greg Kroah-Hartman
2012-04-25 18:14 ` Greg Kroah-Hartman
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=4FA2149A.9030803@vflare.org \
--to=ngupta@vflare.org \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sjenning@linux.vnet.ibm.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.