All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Wen Congyang <wency@cn.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org,
	len.brown@intel.com, benh@kernel.crashing.org, paulus@samba.org,
	cl@linux.com, minchan.kim@gmail.com, akpm@linux-foundation.org
Subject: Re: [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages
Date: Thu, 28 Jun 2012 15:01:38 +0900	[thread overview]
Message-ID: <4FEBF342.9030303@jp.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rzRthh+hpKWAVF9OyL+P_NhFw4y+W-tF3j0zB8pr0QjA@mail.gmail.com>

Hi Kosaki-san,

2012/06/28 14:27, KOSAKI Motohiro wrote:
> On Thu, Jun 28, 2012 at 1:06 AM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp.fujitsu.com> wrote:
>> Hi Wen,
>>
>> 2012/06/27 17:49, Wen Congyang wrote:
>>> At 06/27/2012 01:44 PM, Yasuaki Ishimatsu Wrote:
>>>> When offline_pages() is called to offlined memory, the function fails since
>>>> all memory has been offlined. In this case, the function should succeed.
>>>> The patch adds the check function into offline_pages().
>>>
>>> You miss such case: some pages are online, while some pages are offline.
>>> offline_pages() will fail too in such case.
>>
>> You are right. But current code fails, when the function is called to offline
>> memory. In this case, the function should succeed. So the patch confirms
>> whether the memory was offlined or not. And if memory has already been
>> offlined, offline_pages return 0.
>
> Can you please explain why the caller can't check it? I hope to avoid
> an ignorance
> as far as we can.

Of course, caller side can check it. But there is a possibility that
offline_pages() is called by many functions. So I do not think that it
is good that all functions which call offline_pages() check it.

Thanks,
Yasuaki Ishimatsu


WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: len.brown@intel.com, Wen Congyang <wency@cn.fujitsu.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, paulus@samba.org, minchan.kim@gmail.com,
	cl@linux.com, linuxppc-dev@lists.ozlabs.org,
	akpm@linux-foundation.org
Subject: Re: [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages
Date: Thu, 28 Jun 2012 15:01:38 +0900	[thread overview]
Message-ID: <4FEBF342.9030303@jp.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rzRthh+hpKWAVF9OyL+P_NhFw4y+W-tF3j0zB8pr0QjA@mail.gmail.com>

Hi Kosaki-san,

2012/06/28 14:27, KOSAKI Motohiro wrote:
> On Thu, Jun 28, 2012 at 1:06 AM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp.fujitsu.com> wrote:
>> Hi Wen,
>>
>> 2012/06/27 17:49, Wen Congyang wrote:
>>> At 06/27/2012 01:44 PM, Yasuaki Ishimatsu Wrote:
>>>> When offline_pages() is called to offlined memory, the function fails since
>>>> all memory has been offlined. In this case, the function should succeed.
>>>> The patch adds the check function into offline_pages().
>>>
>>> You miss such case: some pages are online, while some pages are offline.
>>> offline_pages() will fail too in such case.
>>
>> You are right. But current code fails, when the function is called to offline
>> memory. In this case, the function should succeed. So the patch confirms
>> whether the memory was offlined or not. And if memory has already been
>> offlined, offline_pages return 0.
>
> Can you please explain why the caller can't check it? I hope to avoid
> an ignorance
> as far as we can.

Of course, caller side can check it. But there is a possibility that
offline_pages() is called by many functions. So I do not think that it
is good that all functions which call offline_pages() check it.

Thanks,
Yasuaki Ishimatsu

WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Wen Congyang <wency@cn.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org,
	len.brown@intel.com, benh@kernel.crashing.org, paulus@samba.org,
	cl@linux.com, minchan.kim@gmail.com, akpm@linux-foundation.org
Subject: Re: [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages
Date: Thu, 28 Jun 2012 15:01:38 +0900	[thread overview]
Message-ID: <4FEBF342.9030303@jp.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rzRthh+hpKWAVF9OyL+P_NhFw4y+W-tF3j0zB8pr0QjA@mail.gmail.com>

Hi Kosaki-san,

2012/06/28 14:27, KOSAKI Motohiro wrote:
> On Thu, Jun 28, 2012 at 1:06 AM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp.fujitsu.com> wrote:
>> Hi Wen,
>>
>> 2012/06/27 17:49, Wen Congyang wrote:
>>> At 06/27/2012 01:44 PM, Yasuaki Ishimatsu Wrote:
>>>> When offline_pages() is called to offlined memory, the function fails since
>>>> all memory has been offlined. In this case, the function should succeed.
>>>> The patch adds the check function into offline_pages().
>>>
>>> You miss such case: some pages are online, while some pages are offline.
>>> offline_pages() will fail too in such case.
>>
>> You are right. But current code fails, when the function is called to offline
>> memory. In this case, the function should succeed. So the patch confirms
>> whether the memory was offlined or not. And if memory has already been
>> offlined, offline_pages return 0.
>
> Can you please explain why the caller can't check it? I hope to avoid
> an ignorance
> as far as we can.

Of course, caller side can check it. But there is a possibility that
offline_pages() is called by many functions. So I do not think that it
is good that all functions which call offline_pages() check it.

Thanks,
Yasuaki Ishimatsu

--
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: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Wen Congyang <wency@cn.fujitsu.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
	<linux-acpi@vger.kernel.org>, <len.brown@intel.com>,
	<benh@kernel.crashing.org>, <paulus@samba.org>, <cl@linux.com>,
	<minchan.kim@gmail.com>, <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages
Date: Thu, 28 Jun 2012 15:01:38 +0900	[thread overview]
Message-ID: <4FEBF342.9030303@jp.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rzRthh+hpKWAVF9OyL+P_NhFw4y+W-tF3j0zB8pr0QjA@mail.gmail.com>

Hi Kosaki-san,

2012/06/28 14:27, KOSAKI Motohiro wrote:
> On Thu, Jun 28, 2012 at 1:06 AM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp.fujitsu.com> wrote:
>> Hi Wen,
>>
>> 2012/06/27 17:49, Wen Congyang wrote:
>>> At 06/27/2012 01:44 PM, Yasuaki Ishimatsu Wrote:
>>>> When offline_pages() is called to offlined memory, the function fails since
>>>> all memory has been offlined. In this case, the function should succeed.
>>>> The patch adds the check function into offline_pages().
>>>
>>> You miss such case: some pages are online, while some pages are offline.
>>> offline_pages() will fail too in such case.
>>
>> You are right. But current code fails, when the function is called to offline
>> memory. In this case, the function should succeed. So the patch confirms
>> whether the memory was offlined or not. And if memory has already been
>> offlined, offline_pages return 0.
>
> Can you please explain why the caller can't check it? I hope to avoid
> an ignorance
> as far as we can.

Of course, caller side can check it. But there is a possibility that
offline_pages() is called by many functions. So I do not think that it
is good that all functions which call offline_pages() check it.

Thanks,
Yasuaki Ishimatsu


  reply	other threads:[~2012-06-28  6:02 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  5:39 [RFC PATCH 0/12] memory-hotplug : hot-remove physical memory Yasuaki Ishimatsu
2012-06-27  5:39 ` Yasuaki Ishimatsu
2012-06-27  5:39 ` Yasuaki Ishimatsu
2012-06-27  5:42 ` [RFC PATCH 1/12] memory-hotplug : rename remove_memory to offline_memory Yasuaki Ishimatsu
2012-06-27  5:42   ` Yasuaki Ishimatsu
2012-06-27  5:42   ` Yasuaki Ishimatsu
2012-06-27  5:42   ` Yasuaki Ishimatsu
2012-06-27  6:10   ` David Rientjes
2012-06-27  6:10     ` David Rientjes
2012-06-27  6:10     ` David Rientjes
2012-06-27  7:14   ` Wen Congyang
2012-06-27  7:14     ` Wen Congyang
2012-06-27  7:14     ` Wen Congyang
2012-06-27  8:47     ` Wen Congyang
2012-06-27  8:47       ` Wen Congyang
2012-06-27  8:47       ` Wen Congyang
2012-06-28  3:01       ` Yasuaki Ishimatsu
2012-06-28  3:01         ` Yasuaki Ishimatsu
2012-06-28  3:01         ` Yasuaki Ishimatsu
2012-06-28  3:25         ` Wen Congyang
2012-06-28  3:25           ` Wen Congyang
2012-06-28  3:25           ` Wen Congyang
2012-06-28  4:50           ` Yasuaki Ishimatsu
2012-06-28  4:50             ` Yasuaki Ishimatsu
2012-06-28  4:50             ` Yasuaki Ishimatsu
2012-06-28  4:50             ` Yasuaki Ishimatsu
2012-06-27  5:44 ` [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages Yasuaki Ishimatsu
2012-06-27  5:44   ` Yasuaki Ishimatsu
2012-06-27  5:44   ` Yasuaki Ishimatsu
2012-06-27  5:44   ` Yasuaki Ishimatsu
2012-06-27  6:16   ` David Rientjes
2012-06-27  6:16     ` David Rientjes
2012-06-27  6:16     ` David Rientjes
2012-06-28  7:01     ` Yasuaki Ishimatsu
2012-06-28  7:01       ` Yasuaki Ishimatsu
2012-06-28  7:01       ` Yasuaki Ishimatsu
2012-06-27  8:49   ` Wen Congyang
2012-06-27  8:49     ` Wen Congyang
2012-06-27  8:49     ` Wen Congyang
2012-06-28  5:06     ` Yasuaki Ishimatsu
2012-06-28  5:06       ` Yasuaki Ishimatsu
2012-06-28  5:06       ` Yasuaki Ishimatsu
2012-06-28  5:06       ` Yasuaki Ishimatsu
2012-06-28  5:27       ` KOSAKI Motohiro
2012-06-28  5:27         ` KOSAKI Motohiro
2012-06-28  5:27         ` KOSAKI Motohiro
2012-06-28  6:01         ` Yasuaki Ishimatsu [this message]
2012-06-28  6:01           ` Yasuaki Ishimatsu
2012-06-28  6:01           ` Yasuaki Ishimatsu
2012-06-28  6:01           ` Yasuaki Ishimatsu
2012-06-28  5:26   ` KOSAKI Motohiro
2012-06-28  5:26     ` KOSAKI Motohiro
2012-06-28  5:26     ` KOSAKI Motohiro
2012-06-28  5:26     ` KOSAKI Motohiro
2012-06-28  6:51     ` Yasuaki Ishimatsu
2012-06-28  6:51       ` Yasuaki Ishimatsu
2012-06-28  6:51       ` Yasuaki Ishimatsu
2012-06-30 15:46   ` Jiang Liu
2012-06-30 15:46     ` Jiang Liu
2012-06-30 15:46     ` Jiang Liu
2012-07-02  2:53     ` Yasuaki Ishimatsu
2012-07-02  2:53       ` Yasuaki Ishimatsu
2012-07-02  2:53       ` Yasuaki Ishimatsu
2012-07-02  2:53       ` Yasuaki Ishimatsu
2012-06-30 15:51   ` Jiang Liu
2012-06-30 15:51     ` Jiang Liu
2012-06-30 15:51     ` Jiang Liu
2012-07-02  2:56     ` Yasuaki Ishimatsu
2012-07-02  2:56       ` Yasuaki Ishimatsu
2012-07-02  2:56       ` Yasuaki Ishimatsu
2012-06-27  5:45 ` [RFC PATCH 3/12] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove Yasuaki Ishimatsu
2012-06-27  5:45   ` Yasuaki Ishimatsu
2012-06-27  5:45   ` Yasuaki Ishimatsu
2012-06-27  5:45   ` Yasuaki Ishimatsu
2012-06-27  5:47 ` [RFC PATCH 4/12] memory-hotplug : remove /sys/firmware/memmap/X sysfs Yasuaki Ishimatsu
2012-06-27  5:47   ` Yasuaki Ishimatsu
2012-06-27  5:47   ` Yasuaki Ishimatsu
2012-06-27  5:47   ` Yasuaki Ishimatsu
2012-06-28  6:32   ` Wen Congyang
2012-06-28  6:32     ` Wen Congyang
2012-06-28  6:32     ` Wen Congyang
2012-06-28  8:07     ` Yasuaki Ishimatsu
2012-06-28  8:07       ` Yasuaki Ishimatsu
2012-06-28  8:07       ` Yasuaki Ishimatsu
2012-06-28  8:38       ` Wen Congyang
2012-06-28  8:38         ` Wen Congyang
2012-06-28  8:38         ` Wen Congyang
2012-06-29  3:09         ` Yasuaki Ishimatsu
2012-06-29  3:09           ` Yasuaki Ishimatsu
2012-06-29  3:09           ` Yasuaki Ishimatsu
2012-06-27  5:48 ` [RFC PATCH 5/12] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks Yasuaki Ishimatsu
2012-06-27  5:48   ` Yasuaki Ishimatsu
2012-06-27  5:48   ` Yasuaki Ishimatsu
2012-06-27  5:52 ` [RFC PATCH 6/12] memory-hotplug : remove_memory calls __remove_pages Yasuaki Ishimatsu
2012-06-27  5:52   ` Yasuaki Ishimatsu
2012-06-27  5:52   ` Yasuaki Ishimatsu
2012-06-27  5:52   ` Yasuaki Ishimatsu
2012-06-27  5:53 ` [RFC PATCH 7/12] memory-hotplug : check page type in get_page_bootmem Yasuaki Ishimatsu
2012-06-27  5:53   ` Yasuaki Ishimatsu
2012-06-27  5:53   ` Yasuaki Ishimatsu
2012-06-27  5:54 ` [RFC PATCH 8/12] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap Yasuaki Ishimatsu
2012-06-27  5:54   ` Yasuaki Ishimatsu
2012-06-27  5:54   ` Yasuaki Ishimatsu
2012-06-27  5:54   ` Yasuaki Ishimatsu
2012-06-27  5:55 ` [RFC PATCH 9/12] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap Yasuaki Ishimatsu
2012-06-27  5:55   ` Yasuaki Ishimatsu
2012-06-27  5:55   ` Yasuaki Ishimatsu
2012-06-27  5:55   ` Yasuaki Ishimatsu
2012-06-27  5:56 ` [RFC PATCH 10/12] memory-hotplug : free memmap " Yasuaki Ishimatsu
2012-06-27  5:56   ` Yasuaki Ishimatsu
2012-06-27  5:56   ` Yasuaki Ishimatsu
2012-06-30 15:58   ` Jiang Liu
2012-06-30 15:58     ` Jiang Liu
2012-06-30 15:58     ` Jiang Liu
2012-07-02  3:01     ` Yasuaki Ishimatsu
2012-07-02  3:01       ` Yasuaki Ishimatsu
2012-07-02  3:01       ` Yasuaki Ishimatsu
2012-07-02  3:01       ` Yasuaki Ishimatsu
2012-06-27  5:57 ` [RFC PATCH 11/12] memory-hotplug : add node_device_release Yasuaki Ishimatsu
2012-06-27  5:57   ` Yasuaki Ishimatsu
2012-06-27  5:57   ` Yasuaki Ishimatsu
2012-06-27  5:57   ` Yasuaki Ishimatsu
2012-06-27  5:59 ` [RFC PATCH 12/12] memory-hotplug : remove sysfs file of node Yasuaki Ishimatsu
2012-06-27  5:59   ` Yasuaki Ishimatsu
2012-06-27  5:59   ` Yasuaki Ishimatsu
2012-06-27  5:59   ` 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=4FEBF342.9030303@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=cl@linux.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=minchan.kim@gmail.com \
    --cc=paulus@samba.org \
    --cc=wency@cn.fujitsu.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.