From: Yasuaki Ishimatsu <isimatu.yasuaki@jp•fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
Cc: linux-s390@vger•kernel.org, linux-ia64@vger•kernel.org,
wency@cn•fujitsu.com, linux-acpi@vger•kernel.org,
linux-sh@vger•kernel.org, len.brown@intel•com, x86@kernel•org,
Ni zhan Chen <nizhan.chen@gmail•com>,
linux-kernel@vger•kernel.org, cmetcalf@tilera•com,
linux-mm@kvack•org, paulus@samba•org, minchan.kim@gmail•com,
rientjes@google•com, sparclinux@vger•kernel.org, cl@linux•com,
linuxppc-dev@lists•ozlabs.org, akpm@linux-foundation•org,
liuj97@gmail•com
Subject: Re: [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()
Date: Tue, 2 Oct 2012 10:18:56 +0900 [thread overview]
Message-ID: <506A4100.7070305@jp.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=oJ_Jmjqcdr4cPJghf7PX+vfmZe=CV2sdQQhS5agzG15w@mail.gmail.com>
Hi Kosaki-san,
2012/09/29 7:15, KOSAKI Motohiro wrote:
> On Thu, Sep 27, 2012 at 11:50 PM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp•fujitsu.com> wrote:
>> Hi Chen,
>>
>>
>> 2012/09/28 11:22, Ni zhan Chen wrote:
>>>
>>> On 09/05/2012 05:25 PM, wency@cn•fujitsu.com wrote:
>>>>
>>>> From: Yasuaki Ishimatsu <isimatu.yasuaki@jp•fujitsu.com>
>>>>
>>>> remove_memory() only try to offline pages. It is called in two cases:
>>>> 1. hot remove a memory device
>>>> 2. echo offline >/sys/devices/system/memory/memoryXX/state
>>>>
>>>> In the 1st case, we should also change memory block's state, and notify
>>>> the userspace that the memory block's state is changed after offlining
>>>> pages.
>>>>
>>>> So rename remove_memory() to offline_memory()/offline_pages(). And in
>>>> the 1st case, offline_memory() will be used. The function
>>>> offline_memory()
>>>> is not implemented. In the 2nd case, offline_pages() will be used.
>>>
>>>
>>> But this time there is not a function associated with add_memory.
>>
>>
>> To associate with add_memory() later, we renamed it.
>
> Then, you introduced bisect breakage. It is definitely unacceptable.
What is "bisect breakage" meaning?
Thanks,
Yasuaki Ishimatsu
>
> NAK.
>
next prev parent reply other threads:[~2012-10-02 1:19 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 9:25 [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory wency
2012-09-05 9:25 ` [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages() wency
2012-09-28 2:22 ` Ni zhan Chen
2012-09-28 3:50 ` Yasuaki Ishimatsu
2012-09-28 22:15 ` KOSAKI Motohiro
2012-10-02 1:18 ` Yasuaki Ishimatsu [this message]
2012-10-02 17:29 ` KOSAKI Motohiro
2012-09-05 9:25 ` [RFC v9 PATCH 02/21] memory-hotplug: implement offline_memory() wency
2012-09-05 9:25 ` [RFC v9 PATCH 03/21] memory-hotplug: store the node id in acpi_memory_device wency
2012-09-28 3:21 ` Ni zhan Chen
2012-10-01 7:38 ` Yasuaki Ishimatsu
2012-09-05 9:25 ` [RFC v9 PATCH 04/21] memory-hotplug: offline and remove memory when removing the memory device wency
2012-09-28 4:48 ` Ni zhan Chen
2012-09-05 9:25 ` [RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not wency
2012-09-11 2:15 ` Wen Congyang
2012-09-11 2:24 ` Yasuaki Ishimatsu
2012-09-11 2:46 ` Wen Congyang
2012-09-28 3:37 ` Ni zhan Chen
2012-09-05 9:25 ` [RFC v9 PATCH 06/21] memory-hotplug: export the function acpi_bus_remove() wency
2012-10-02 0:34 ` Ni zhan Chen
2012-10-02 17:28 ` KOSAKI Motohiro
2012-09-05 9:25 ` [RFC v9 PATCH 07/21] memory-hotplug: call acpi_bus_remove() to remove memory device wency
2012-09-05 9:25 ` [RFC v9 PATCH 08/21] memory-hotplug: remove /sys/firmware/memmap/X sysfs wency
2012-09-05 9:25 ` [RFC v9 PATCH 09/21] memory-hotplug: does not release memory region in PAGES_PER_SECTION chunks wency
2012-09-05 9:25 ` [RFC v9 PATCH 10/21] memory-hotplug: add memory_block_release wency
2012-09-05 9:25 ` [RFC v9 PATCH 11/21] memory-hotplug: remove_memory calls __remove_pages wency
2012-09-05 9:25 ` [RFC v9 PATCH 12/21] memory-hotplug: introduce new function arch_remove_memory() wency
2012-09-05 9:25 ` [RFC v9 PATCH 13/21] memory-hotplug: check page type in get_page_bootmem wency
2012-09-29 2:15 ` Ni zhan Chen
2012-10-01 3:03 ` Yasuaki Ishimatsu
2012-10-02 12:24 ` Ni zhan Chen
2012-09-05 9:25 ` [RFC v9 PATCH 14/21] memory-hotplug: move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap wency
2012-09-05 9:25 ` [RFC v9 PATCH 15/21] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap wency
2012-09-05 9:25 ` [RFC v9 PATCH 16/21] memory-hotplug: free memmap " wency
2012-10-02 4:21 ` Ni zhan Chen
2012-10-04 6:26 ` Yasuaki Ishimatsu
2012-10-06 14:18 ` Ni zhan Chen
2012-09-05 9:25 ` [RFC v9 PATCH 17/21] memory_hotplug: clear zone when the memory is removed wency
2012-09-05 9:25 ` [RFC v9 PATCH 18/21] memory-hotplug: add node_device_release wency
2012-09-05 9:25 ` [RFC v9 PATCH 19/21] memory-hotplug: remove sysfs file of node wency
2012-09-05 9:25 ` [RFC v9 PATCH 20/21] memory-hotplug: clear hwpoisoned flag when onlining pages wency
2012-09-06 7:27 ` andywu106建国
2012-09-06 8:41 ` Wen Congyang
2012-09-05 9:25 ` [RFC v9 PATCH 21/21] memory-hotplug: auto offline page_cgroup when onlining memory block failed wency
2012-09-26 16:46 ` [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory Vasilis Liaskovitis
2012-09-27 0:59 ` Wen Congyang
2012-09-27 6:37 ` Wen Congyang
2012-09-27 10:35 ` Vasilis Liaskovitis
2012-09-28 1:41 ` Wen Congyang
2012-10-09 6:16 ` Wen Congyang
2012-10-09 8:11 ` Wen Congyang
2012-09-26 16:58 ` Vasilis Liaskovitis
2012-09-27 1:03 ` Wen Congyang
2012-09-27 8:53 ` Wen Congyang
2012-09-27 10:06 ` Wen Congyang
2012-09-27 11:02 ` Vasilis Liaskovitis
2012-09-29 3:45 ` Ni zhan Chen
2012-09-29 8:19 ` Ni zhan Chen
2012-10-01 4:44 ` Yasuaki Ishimatsu
2012-10-01 23:45 ` Ni zhan Chen
2012-10-02 0:02 ` 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=506A4100.7070305@jp.fujitsu.com \
--to=isimatu.yasuaki@jp$(echo .)fujitsu.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=cl@linux$(echo .)com \
--cc=cmetcalf@tilera$(echo .)com \
--cc=kosaki.motohiro@jp$(echo .)fujitsu.com \
--cc=len.brown@intel$(echo .)com \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=liuj97@gmail$(echo .)com \
--cc=minchan.kim@gmail$(echo .)com \
--cc=nizhan.chen@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=rientjes@google$(echo .)com \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=wency@cn$(echo .)fujitsu.com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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