On 2012/8/14 22:14, Christoph Lameter wrote:
> On Tue, 14 Aug 2012, Hanjun Guo wrote:
>
>> N_NORMAL_MEMORY means !LRU allocs possible.
>
> Ok. I am fine with that change. However this is a significant change that
> needs to be mentioned prominently in the changelog and there need to be
> some
On 2012/8/14 22:14, Christoph Lameter wrote:
On Tue, 14 Aug 2012, Hanjun Guo wrote:
N_NORMAL_MEMORY means !LRU allocs possible.
Ok. I am fine with that change. However this is a significant change that
needs to be mentioned prominently in the changelog and there need to be
some comments
On Tue, 14 Aug 2012, Hanjun Guo wrote:
> N_NORMAL_MEMORY means !LRU allocs possible.
Ok. I am fine with that change. However this is a significant change that
needs to be mentioned prominently in the changelog and there need to be
some comments explaining the meaning of these flags clearly in
On 2012/8/10 22:12, Christoph Lameter (Open Source) wrote:
> On Fri, 10 Aug 2012, Hanjun Guo wrote:
>
>> On 2012/8/9 22:06, Christoph Lameter (Open Source) wrote:
>>> On Thu, 9 Aug 2012, Hanjun Guo wrote:
>>>
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to
On 2012/8/10 22:12, Christoph Lameter (Open Source) wrote:
On Fri, 10 Aug 2012, Hanjun Guo wrote:
On 2012/8/9 22:06, Christoph Lameter (Open Source) wrote:
On Thu, 9 Aug 2012, Hanjun Guo wrote:
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to distinguish between normal
On Tue, 14 Aug 2012, Hanjun Guo wrote:
N_NORMAL_MEMORY means !LRU allocs possible.
Ok. I am fine with that change. However this is a significant change that
needs to be mentioned prominently in the changelog and there need to be
some comments explaining the meaning of these flags clearly in the
On Fri, 10 Aug 2012, Hanjun Guo wrote:
> On 2012/8/9 22:06, Christoph Lameter (Open Source) wrote:
> > On Thu, 9 Aug 2012, Hanjun Guo wrote:
> >
> >> Now, We have node masks for both N_NORMAL_MEMORY and
> >> N_HIGH_MEMORY to distinguish between normal and highmem on platforms such
> >> as x86.
>
Hi Isimatuļ¼
We have worked out a changeset to enable offlinable node, which
is based on a new ACPI based hotplug framework
(http://www.spinics.net/lists/linux-pci/msg16826.html).
Now could hot-add/hot-remove a computer node with CPU/memory/PCI host bridge,
but it's still a prototype and
Hi Guo,
I have a question. How do you create the offlinable node? The current linux
cannot offline all memory on node. So we cannot hit the bug.
Recently Lai sent the following patches which create the movable node.
I think these patches consider the problem.
https://lkml.org/lkml/2012/8/6/113
On 2012/8/9 22:06, Christoph Lameter (Open Source) wrote:
> On Thu, 9 Aug 2012, Hanjun Guo wrote:
>
>> Now, We have node masks for both N_NORMAL_MEMORY and
>> N_HIGH_MEMORY to distinguish between normal and highmem on platforms such as
>> x86.
>> But we still don't have such a mechanism to
On 2012/8/9 22:06, Christoph Lameter (Open Source) wrote:
On Thu, 9 Aug 2012, Hanjun Guo wrote:
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to distinguish between normal and highmem on platforms such as
x86.
But we still don't have such a mechanism to distinguish
Hi Guo,
I have a question. How do you create the offlinable node? The current linux
cannot offline all memory on node. So we cannot hit the bug.
Recently Lai sent the following patches which create the movable node.
I think these patches consider the problem.
https://lkml.org/lkml/2012/8/6/113
Hi Isimatuļ¼
We have worked out a changeset to enable offlinable node, which
is based on a new ACPI based hotplug framework
(http://www.spinics.net/lists/linux-pci/msg16826.html).
Now could hot-add/hot-remove a computer node with CPU/memory/PCI host bridge,
but it's still a prototype and
On Fri, 10 Aug 2012, Hanjun Guo wrote:
On 2012/8/9 22:06, Christoph Lameter (Open Source) wrote:
On Thu, 9 Aug 2012, Hanjun Guo wrote:
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to distinguish between normal and highmem on platforms such
as x86.
But we still
On Thu, 9 Aug 2012, Hanjun Guo wrote:
> Now, We have node masks for both N_NORMAL_MEMORY and
> N_HIGH_MEMORY to distinguish between normal and highmem on platforms such as
> x86.
> But we still don't have such a mechanism to distinguish between "normal" and
> "movable"
> memory.
What is the
On Thu, 9 Aug 2012, Hanjun Guo wrote:
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to distinguish between normal and highmem on platforms such as
x86.
But we still don't have such a mechanism to distinguish between normal and
movable
memory.
What is the exact
From: Wu Jianguo
Hi all,
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to distinguish between normal and highmem on platforms such as
x86.
But we still don't have such a mechanism to distinguish between "normal" and
"movable"
memory.
As suggested by Christoph Lameter in
From: Wu Jianguo wujian...@huawei.com
Hi all,
Now, We have node masks for both N_NORMAL_MEMORY and
N_HIGH_MEMORY to distinguish between normal and highmem on platforms such as
x86.
But we still don't have such a mechanism to distinguish between normal and
movable
memory.
As suggested by
18 matches
Mail list logo
