On Wed, Jun 14, 2017 at 11:24:38AM +0200, Michal Hocko wrote:
>On Wed 14-06-17 17:12:06, Wei Yang wrote:
>> On Wed, Jun 14, 2017 at 08:32:06AM +0200, Michal Hocko wrote:
>> >On Wed 14-06-17 14:12:59, Wei Yang wrote:
>> >[...]
>> >> Hi, Michal
>> >>
>> >> Not sure you missed this one or you think
On Wed, Jun 14, 2017 at 11:24:38AM +0200, Michal Hocko wrote:
>On Wed 14-06-17 17:12:06, Wei Yang wrote:
>> On Wed, Jun 14, 2017 at 08:32:06AM +0200, Michal Hocko wrote:
>> >On Wed 14-06-17 14:12:59, Wei Yang wrote:
>> >[...]
>> >> Hi, Michal
>> >>
>> >> Not sure you missed this one or you think
On Wed 14-06-17 17:12:06, Wei Yang wrote:
> On Wed, Jun 14, 2017 at 08:32:06AM +0200, Michal Hocko wrote:
> >On Wed 14-06-17 14:12:59, Wei Yang wrote:
> >[...]
> >> Hi, Michal
> >>
> >> Not sure you missed this one or you think this is fine.
> >>
> >> Hmm... this will not happen since we must
On Wed 14-06-17 17:12:06, Wei Yang wrote:
> On Wed, Jun 14, 2017 at 08:32:06AM +0200, Michal Hocko wrote:
> >On Wed 14-06-17 14:12:59, Wei Yang wrote:
> >[...]
> >> Hi, Michal
> >>
> >> Not sure you missed this one or you think this is fine.
> >>
> >> Hmm... this will not happen since we must
On Wed, Jun 14, 2017 at 08:32:06AM +0200, Michal Hocko wrote:
>On Wed 14-06-17 14:12:59, Wei Yang wrote:
>[...]
>> Hi, Michal
>>
>> Not sure you missed this one or you think this is fine.
>>
>> Hmm... this will not happen since we must offline a whole memory_block?
>
>yes
>
>> So the
On Wed, Jun 14, 2017 at 08:32:06AM +0200, Michal Hocko wrote:
>On Wed 14-06-17 14:12:59, Wei Yang wrote:
>[...]
>> Hi, Michal
>>
>> Not sure you missed this one or you think this is fine.
>>
>> Hmm... this will not happen since we must offline a whole memory_block?
>
>yes
>
>> So the
On Wed 14-06-17 14:12:59, Wei Yang wrote:
[...]
> Hi, Michal
>
> Not sure you missed this one or you think this is fine.
>
> Hmm... this will not happen since we must offline a whole memory_block?
yes
> So the memory_hotplug/unplug unit is memory_block instead of mem_section?
yes.
--
Michal
On Wed 14-06-17 14:12:59, Wei Yang wrote:
[...]
> Hi, Michal
>
> Not sure you missed this one or you think this is fine.
>
> Hmm... this will not happen since we must offline a whole memory_block?
yes
> So the memory_hotplug/unplug unit is memory_block instead of mem_section?
yes.
--
Michal
On Mon, Jun 12, 2017 at 08:49:53AM +0200, Michal Hocko wrote:
>On Sat 10-06-17 22:58:21, Wei Yang wrote:
>> On Sat, Jun 10, 2017 at 5:56 PM, Wei Yang wrote:
>[...]
>> > Hmm... one question about the memory_block behavior.
>> >
>> > In case one memory_block contains more
On Mon, Jun 12, 2017 at 08:49:53AM +0200, Michal Hocko wrote:
>On Sat 10-06-17 22:58:21, Wei Yang wrote:
>> On Sat, Jun 10, 2017 at 5:56 PM, Wei Yang wrote:
>[...]
>> > Hmm... one question about the memory_block behavior.
>> >
>> > In case one memory_block contains more than one memory section.
On Sat, Jun 10, 2017 at 05:56:02PM +0800, Wei Yang wrote:
>On Mon, May 15, 2017 at 4:58 PM, Michal Hocko wrote:
>> From: Michal Hocko
>>
>> device memory hotplug hooks into regular memory hotplug only half way.
>> It needs memory sections to track struct pages
On Sat, Jun 10, 2017 at 05:56:02PM +0800, Wei Yang wrote:
>On Mon, May 15, 2017 at 4:58 PM, Michal Hocko wrote:
>> From: Michal Hocko
>>
>> device memory hotplug hooks into regular memory hotplug only half way.
>> It needs memory sections to track struct pages but there is no
>> need/desire to
On Sat 10-06-17 22:58:21, Wei Yang wrote:
> On Sat, Jun 10, 2017 at 5:56 PM, Wei Yang wrote:
[...]
> > Hmm... one question about the memory_block behavior.
> >
> > In case one memory_block contains more than one memory section.
> > If one section is "device zone", the
On Sat 10-06-17 22:58:21, Wei Yang wrote:
> On Sat, Jun 10, 2017 at 5:56 PM, Wei Yang wrote:
[...]
> > Hmm... one question about the memory_block behavior.
> >
> > In case one memory_block contains more than one memory section.
> > If one section is "device zone", the whole memory_block is not
On Sat, Jun 10, 2017 at 5:56 PM, Wei Yang wrote:
> On Mon, May 15, 2017 at 4:58 PM, Michal Hocko wrote:
>> From: Michal Hocko
>>
>> device memory hotplug hooks into regular memory hotplug only half way.
>> It needs memory sections
On Sat, Jun 10, 2017 at 5:56 PM, Wei Yang wrote:
> On Mon, May 15, 2017 at 4:58 PM, Michal Hocko wrote:
>> From: Michal Hocko
>>
>> device memory hotplug hooks into regular memory hotplug only half way.
>> It needs memory sections to track struct pages but there is no
>> need/desire to
On Mon, May 15, 2017 at 4:58 PM, Michal Hocko wrote:
> From: Michal Hocko
>
> device memory hotplug hooks into regular memory hotplug only half way.
> It needs memory sections to track struct pages but there is no
> need/desire to associate those sections with
On Mon, May 15, 2017 at 4:58 PM, Michal Hocko wrote:
> From: Michal Hocko
>
> device memory hotplug hooks into regular memory hotplug only half way.
> It needs memory sections to track struct pages but there is no
> need/desire to associate those sections with memory blocks and export
> them to
From: Michal Hocko
device memory hotplug hooks into regular memory hotplug only half way.
It needs memory sections to track struct pages but there is no
need/desire to associate those sections with memory blocks and export
them to the userspace via sysfs because they cannot be
From: Michal Hocko
device memory hotplug hooks into regular memory hotplug only half way.
It needs memory sections to track struct pages but there is no
need/desire to associate those sections with memory blocks and export
them to the userspace via sysfs because they cannot be onlined anyway.
20 matches
Mail list logo