From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, linuxram@us.ibm.com,
rientjes@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [Bug fix PATCH v4] Reusing a resource structure allocated by bootmem
Date: Fri, 19 Apr 2013 08:43:55 +0900 [thread overview]
Message-ID: <5170853B.2040807@jp.fujitsu.com> (raw)
In-Reply-To: <1366327735.3824.50.camel@misato.fc.hp.com>
2013/04/19 8:28, Toshi Kani wrote:
> On Fri, 2013-04-19 at 08:33 +0900, Yasuaki Ishimatsu wrote:
> :
>>>
>>>> +static struct resource *get_resource(gfp_t flags)
>>>> +{
>>>> + struct resource *res = NULL;
>>>> +
>>>> + spin_lock(&bootmem_resource_lock);
>>>> + if (bootmem_resource.sibling) {
>>>> + res = bootmem_resource.sibling;
>>>> + bootmem_resource.sibling = res->sibling;
>>>> + memset(res, 0, sizeof(struct resource));
>>>> + }
>>>> + spin_unlock(&bootmem_resource_lock);
>>>
>>
>>> I prefer to keep memset() outside of the spin lock.
>>>
>>> spin_lock(&bootmem_resource_lock);
>>> if (..) {
>>> :
>>> spin_unlock(&bootmem_resource_lock);
>>> memset(res, 0, sizeof(struct resource));
>>> } else {
>>> spin_unlock(&bootmem_resource_lock);
>>> res = kzalloc(sizeof(struct resource), flags);
>>> }
>>
>> Hmm. It is a little ugly. How about it?
>>
>> spin_lock(&bootmem_resource_lock);
>> if (bootmem_resource.sibling) {
>> res = bootmem_resource.sibling;
>> bootmem_resource.sibling = res->sibling;
>> }
>> spin_unlock(&bootmem_resource_lock);
>>
>> if (res)
>> memset(res, 0, sizeof(struct resource));
>> else
>> res = kzalloc(sizeof(struct resource), flags);
>
> Sounds good to me.
Great. I'll update it.
Thanks,
Yasuaki Ishimatsu
>
> Thanks,
> -Toshi
>
>
--
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: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: <akpm@linux-foundation.org>, <linuxram@us.ibm.com>,
<rientjes@google.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [Bug fix PATCH v4] Reusing a resource structure allocated by bootmem
Date: Fri, 19 Apr 2013 08:43:55 +0900 [thread overview]
Message-ID: <5170853B.2040807@jp.fujitsu.com> (raw)
In-Reply-To: <1366327735.3824.50.camel@misato.fc.hp.com>
2013/04/19 8:28, Toshi Kani wrote:
> On Fri, 2013-04-19 at 08:33 +0900, Yasuaki Ishimatsu wrote:
> :
>>>
>>>> +static struct resource *get_resource(gfp_t flags)
>>>> +{
>>>> + struct resource *res = NULL;
>>>> +
>>>> + spin_lock(&bootmem_resource_lock);
>>>> + if (bootmem_resource.sibling) {
>>>> + res = bootmem_resource.sibling;
>>>> + bootmem_resource.sibling = res->sibling;
>>>> + memset(res, 0, sizeof(struct resource));
>>>> + }
>>>> + spin_unlock(&bootmem_resource_lock);
>>>
>>
>>> I prefer to keep memset() outside of the spin lock.
>>>
>>> spin_lock(&bootmem_resource_lock);
>>> if (..) {
>>> :
>>> spin_unlock(&bootmem_resource_lock);
>>> memset(res, 0, sizeof(struct resource));
>>> } else {
>>> spin_unlock(&bootmem_resource_lock);
>>> res = kzalloc(sizeof(struct resource), flags);
>>> }
>>
>> Hmm. It is a little ugly. How about it?
>>
>> spin_lock(&bootmem_resource_lock);
>> if (bootmem_resource.sibling) {
>> res = bootmem_resource.sibling;
>> bootmem_resource.sibling = res->sibling;
>> }
>> spin_unlock(&bootmem_resource_lock);
>>
>> if (res)
>> memset(res, 0, sizeof(struct resource));
>> else
>> res = kzalloc(sizeof(struct resource), flags);
>
> Sounds good to me.
Great. I'll update it.
Thanks,
Yasuaki Ishimatsu
>
> Thanks,
> -Toshi
>
>
next prev parent reply other threads:[~2013-04-18 23:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 8:36 [Bug fix PATCH v4] Reusing a resource structure allocated by bootmem Yasuaki Ishimatsu
2013-04-18 8:36 ` Yasuaki Ishimatsu
2013-04-18 13:42 ` Johannes Weiner
2013-04-18 13:42 ` Johannes Weiner
2013-04-18 23:21 ` Yasuaki Ishimatsu
2013-04-18 23:21 ` Yasuaki Ishimatsu
2013-04-18 14:23 ` Toshi Kani
2013-04-18 14:23 ` Toshi Kani
2013-04-18 23:33 ` Yasuaki Ishimatsu
2013-04-18 23:33 ` Yasuaki Ishimatsu
2013-04-18 23:28 ` Toshi Kani
2013-04-18 23:28 ` Toshi Kani
2013-04-18 23:43 ` Yasuaki Ishimatsu [this message]
2013-04-18 23:43 ` Yasuaki Ishimatsu
2013-04-19 8:09 ` Yasuaki Ishimatsu
2013-04-19 8:09 ` Yasuaki Ishimatsu
2013-04-19 14:30 ` Toshi Kani
2013-04-19 14:30 ` Toshi Kani
2013-04-23 0:19 ` Yasuaki Ishimatsu
2013-04-23 0:19 ` Yasuaki Ishimatsu
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=5170853B.2040807@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxram@us.ibm.com \
--cc=rientjes@google.com \
--cc=toshi.kani@hp.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.