linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Dave Hansen <dave@sr71.net>,
	Nathan Fontenot <nfont@linux.vnet.ibm.com>,
	Cody P Schafer <cody@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Yinghai Lu <yinghai@kernel.org>,
	Wanpeng Li <liwanp@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 7/7] drivers: base: refactor add_memory_section() to add_memory_block()
Date: Thu, 22 Aug 2013 17:30:56 +0900	[thread overview]
Message-ID: <5215CC40.5060406@jp.fujitsu.com> (raw)
In-Reply-To: <5215C9B3.4090608@jp.fujitsu.com>

(2013/08/22 17:20), Yasuaki Ishimatsu wrote:
> (2013/08/21 2:13), Seth Jennings wrote:
>> Right now memory_dev_init() maintains the memory block pointer
>> between iterations of add_memory_section().  This is nasty.
>>
>> This patch refactors add_memory_section() to become add_memory_block().
>> The refactoring pulls the section scanning out of memory_dev_init()
>> and simplifies the signature.
>>
>> Signed-off-by: Seth Jennings <sjenning@linux.vnet.ibm.com>
>> ---
>>    drivers/base/memory.c | 48 +++++++++++++++++++++---------------------------
>>    1 file changed, 21 insertions(+), 27 deletions(-)
>>
>> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
>> index 7d9d3bc..021283a 100644
>> --- a/drivers/base/memory.c
>> +++ b/drivers/base/memory.c
>> @@ -602,32 +602,31 @@ static int init_memory_block(struct memory_block **memory,
>>    	return ret;
>>    }
>>    
>> -static int add_memory_section(struct mem_section *section,
>> -			struct memory_block **mem_p)
>> +static int add_memory_block(int base_section_nr)
>>    {
>> -	struct memory_block *mem = NULL;
>> -	int scn_nr = __section_nr(section);
>> -	int ret = 0;
>> -
>> -	if (mem_p && *mem_p) {
>> -		if (scn_nr >= (*mem_p)->start_section_nr &&
>> -		    scn_nr <= (*mem_p)->end_section_nr) {
>> -			mem = *mem_p;
>> -		}
>> -	}
>> +	struct memory_block *mem;
>> +	int i, ret, section_count = 0, section_nr;
>>    
>> -	if (mem)
>> -		mem->section_count++;
>> -	else {
>> -		ret = init_memory_block(&mem, section, MEM_ONLINE);
>> -		/* store memory_block pointer for next loop */
>> -		if (!ret && mem_p)
>> -			*mem_p = mem;
>> +	for (i = base_section_nr;
>> +	     (i < base_section_nr + sections_per_block) && i < NR_MEM_SECTIONS;
>> +	     i++) {
>> +		if (!present_section_nr(i))
>> +			continue;
>> +		if (section_count == 0)
>> +			section_nr = i;
>> +		section_count++;
>>    	}
>>    
>> -	return ret;
>> +	if (section_count == 0)
>> +		return 0;
>> +	ret = init_memory_block(&mem, __nr_to_section(section_nr), MEM_ONLINE);
>> +	if (ret)
>> +		return ret;
>> +	mem->section_count = section_count;
>> +	return 0;
>>    }
>>    
>> +
>>    /*
>>     * need an interface for the VM to add new memory regions,
>>     * but without onlining it.
>> @@ -733,7 +732,6 @@ int __init memory_dev_init(void)
>>    	int ret;
>>    	int err;
>>    	unsigned long block_sz;
>> -	struct memory_block *mem = NULL;
>>    
>>    	ret = subsys_system_register(&memory_subsys, memory_root_attr_groups);
>>    	if (ret)
>> @@ -747,12 +745,8 @@ int __init memory_dev_init(void)
>>    	 * during boot and have been initialized
>>    	 */
>>    	mutex_lock(&mem_sysfs_mutex);
>> -	for (i = 0; i < NR_MEM_SECTIONS; i++) {
>> -		if (!present_section_nr(i))
>> -			continue;
>> -		/* don't need to reuse memory_block if only one per block */
>> -		err = add_memory_section(__nr_to_section(i),
>> -				 (sections_per_block == 1) ? NULL : &mem);
>> +	for (i = 0; i < NR_MEM_SECTIONS; i += sections_per_block) {
> 
> Why do you remove present_setcion_nr() check?

Sorry for the noise. I understood.
The check was moved into add_memory_section(). So it was removed.

Thanks,
Yasuaki Ishimatsu

> 
>> +		err = add_memory_block(i);
>>    		if (!ret)
> 
> Thanks,
> Yasuaki Ishimatasu
> 
>>    			ret = err;
>>    	}
>>
> 
> 
> --
> 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>
> 


--
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>

  reply	other threads:[~2013-08-22  8:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 17:12 [PATCH 1/7] drivers: base: move mutex lock out of add_memory_section() Seth Jennings
2013-08-20 17:12 ` [PATCH 2/7] drivers: base: remove unneeded variable Seth Jennings
2013-08-20 17:12 ` [PATCH 3/7] drivers: base: use device get/put functions Seth Jennings
2013-08-20 17:13 ` [PATCH 4/7] drivers: base: unshare add_memory_section() from hotplug Seth Jennings
2013-08-20 17:13 ` [PATCH 5/7] drivers: base: reduce add_memory_section() for boot-time only Seth Jennings
2013-08-20 17:13 ` [PATCH 6/7] drivers: base: remove improper get/put in add_memory_section() Seth Jennings
2013-08-20 17:13 ` [PATCH 7/7] drivers: base: refactor add_memory_section() to add_memory_block() Seth Jennings
2013-08-22  8:20   ` Yasuaki Ishimatsu
2013-08-22  8:30     ` Yasuaki Ishimatsu [this message]
2013-08-22 15:11     ` Seth Jennings
2013-08-20 17:24 ` [PATCH 1/7] drivers: base: move mutex lock out of add_memory_section() Seth Jennings
2013-08-21 18:50   ` Greg Kroah-Hartman
2013-08-22  8:44   ` 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=5215CC40.5060406@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=cody@linux.vnet.ibm.com \
    --cc=dave@sr71.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=liwanp@linux.vnet.ibm.com \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sjenning@linux.vnet.ibm.com \
    --cc=yinghai@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