Hi Gerry,
On 25.07.2014 [09:50:01 +0800], Jiang Liu wrote:
>
>
> On 2014/7/25 7:32, Nishanth Aravamudan wrote:
> > On 23.07.2014 [16:20:24 +0800], Jiang Liu wrote:
> >>
> >>
> >> On 2014/7/22 1:57, Nishanth Aravamudan wrote:
> >>> On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
> On Mon,
Hi Gerry,
On 25.07.2014 [09:50:01 +0800], Jiang Liu wrote:
On 2014/7/25 7:32, Nishanth Aravamudan wrote:
On 23.07.2014 [16:20:24 +0800], Jiang Liu wrote:
On 2014/7/22 1:57, Nishanth Aravamudan wrote:
On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23
On 2014/7/25 7:32, Nishanth Aravamudan wrote:
> On 23.07.2014 [16:20:24 +0800], Jiang Liu wrote:
>>
>>
>> On 2014/7/22 1:57, Nishanth Aravamudan wrote:
>>> On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
wrote:
> It seems like
On 23.07.2014 [16:20:24 +0800], Jiang Liu wrote:
>
>
> On 2014/7/22 1:57, Nishanth Aravamudan wrote:
> > On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
> >> On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
> >> wrote:
> >>> It seems like the issue is the order of onlining of resources on
On 23.07.2014 [16:20:24 +0800], Jiang Liu wrote:
On 2014/7/22 1:57, Nishanth Aravamudan wrote:
On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
It seems like the issue is the order of onlining of
On 2014/7/25 7:32, Nishanth Aravamudan wrote:
On 23.07.2014 [16:20:24 +0800], Jiang Liu wrote:
On 2014/7/22 1:57, Nishanth Aravamudan wrote:
On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
It seems like
On 2014/7/22 1:57, Nishanth Aravamudan wrote:
> On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
>> On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
>> wrote:
>>> It seems like the issue is the order of onlining of resources on a
>>> specific x86 platform?
>>
>> Yes. When we online a node
On 2014/7/22 1:57, Nishanth Aravamudan wrote:
On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
It seems like the issue is the order of onlining of resources on a
specific x86 platform?
Yes. When we online
On Mon, Jul 21, 2014 at 10:41:59AM -0700, Tony Luck wrote:
> On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
> wrote:
> > It seems like the issue is the order of onlining of resources on a
> > specific x86 platform?
>
> Yes. When we online a node the BIOS hits us with some ACPI hotplug
On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
> On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
> wrote:
> > It seems like the issue is the order of onlining of resources on a
> > specific x86 platform?
>
> Yes. When we online a node the BIOS hits us with some ACPI hotplug events:
>
>
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
wrote:
> It seems like the issue is the order of onlining of resources on a
> specific x86 platform?
Yes. When we online a node the BIOS hits us with some ACPI hotplug events:
First: Here are some new cpus
Next: Here is some new memory
Last;
Hi Jiang,
On 11.07.2014 [15:37:17 +0800], Jiang Liu wrote:
> Previously we have posted a patch fix a memory crash issue caused by
> memoryless node on x86 platforms, please refer to
> http://comments.gmane.org/gmane.linux.kernel/1687425
>
> As suggested by David Rientjes, the most suitable fix
Hi Jiang,
On 11.07.2014 [15:37:17 +0800], Jiang Liu wrote:
Previously we have posted a patch fix a memory crash issue caused by
memoryless node on x86 platforms, please refer to
http://comments.gmane.org/gmane.linux.kernel/1687425
As suggested by David Rientjes, the most suitable fix for
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
It seems like the issue is the order of onlining of resources on a
specific x86 platform?
Yes. When we online a node the BIOS hits us with some ACPI hotplug events:
First: Here are some new cpus
Next: Here is
On 21.07.2014 [10:41:59 -0700], Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
It seems like the issue is the order of onlining of resources on a
specific x86 platform?
Yes. When we online a node the BIOS hits us with some ACPI
On Mon, Jul 21, 2014 at 10:41:59AM -0700, Tony Luck wrote:
On Mon, Jul 21, 2014 at 10:23 AM, Nishanth Aravamudan
n...@linux.vnet.ibm.com wrote:
It seems like the issue is the order of onlining of resources on a
specific x86 platform?
Yes. When we online a node the BIOS hits us with some
On Sat, 12 Jul 2014, Jiri Kosina wrote:
> I am pretty sure I've seen ppc64 machine with memoryless NUMA node.
>
Yes, Nishanth Aravamudan (now cc'd) has been working diligently on the
problems that have been encountered, including problems in generic kernel
code, on powerpc with memoryless
On Fri, 11 Jul 2014, Peter Zijlstra wrote:
> > There are other cases too.
>
> Are there any sane ones?
>
They are specifically allowed by the ACPI specification to be able to
include only cpus, I/O, networking cards, etc.
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, 11 Jul 2014, Peter Zijlstra wrote:
There are other cases too.
Are there any sane ones?
They are specifically allowed by the ACPI specification to be able to
include only cpus, I/O, networking cards, etc.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
On Sat, 12 Jul 2014, Jiri Kosina wrote:
I am pretty sure I've seen ppc64 machine with memoryless NUMA node.
Yes, Nishanth Aravamudan (now cc'd) has been working diligently on the
problems that have been encountered, including problems in generic kernel
code, on powerpc with memoryless
On 07/11/2014 01:20 PM, Andi Kleen wrote:
> Greg KH writes:
>
>> On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
>>> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
>>>
>>> Why would anybody _ever_ have a memoryless node? That's
On Fri, 11 Jul 2014, Greg KH wrote:
> > On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
> > > Any comments are welcomed!
> >
> > Why would anybody _ever_ have a memoryless node? That's ridiculous.
>
> I'm with Peter here, why would this be a situation that we should even
> support?
On Fri, Jul 11, 2014 at 10:51:06PM +0200, Peter Zijlstra wrote:
> On Fri, Jul 11, 2014 at 01:20:51PM -0700, Andi Kleen wrote:
> > Greg KH writes:
> >
> > > On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
> > >> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
> > >> >
On Fri, Jul 11, 2014 at 01:20:51PM -0700, Andi Kleen wrote:
> Greg KH writes:
>
> > On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
> >> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
> >> > Any comments are welcomed!
> >>
> >> Why would anybody _ever_ have a
Greg KH writes:
> On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
>> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
>> > Any comments are welcomed!
>>
>> Why would anybody _ever_ have a memoryless node? That's ridiculous.
>
> I'm with Peter here, why would this be a
On 07/11/2014 08:33 AM, Greg KH wrote:
> On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
>> > On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
>>> > > Any comments are welcomed!
>> >
>> > Why would anybody _ever_ have a memoryless node? That's ridiculous.
> I'm with
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
> On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
> > Any comments are welcomed!
>
> Why would anybody _ever_ have a memoryless node? That's ridiculous.
I'm with Peter here, why would this be a situation that we should
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
> Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's ridiculous.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Previously we have posted a patch fix a memory crash issue caused by
memoryless node on x86 platforms, please refer to
http://comments.gmane.org/gmane.linux.kernel/1687425
As suggested by David Rientjes, the most suitable fix for the issue
should be to use cpu_to_mem() rather than cpu_to_node()
Previously we have posted a patch fix a memory crash issue caused by
memoryless node on x86 platforms, please refer to
http://comments.gmane.org/gmane.linux.kernel/1687425
As suggested by David Rientjes, the most suitable fix for the issue
should be to use cpu_to_mem() rather than cpu_to_node()
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's ridiculous.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's ridiculous.
I'm with Peter here, why would this be a situation that we should even
On 07/11/2014 08:33 AM, Greg KH wrote:
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's ridiculous.
I'm with Peter here, why
Greg KH gre...@linuxfoundation.org writes:
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's ridiculous.
I'm with Peter here, why
On Fri, Jul 11, 2014 at 01:20:51PM -0700, Andi Kleen wrote:
Greg KH gre...@linuxfoundation.org writes:
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have
On Fri, Jul 11, 2014 at 10:51:06PM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 01:20:51PM -0700, Andi Kleen wrote:
Greg KH gre...@linuxfoundation.org writes:
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu
On Fri, 11 Jul 2014, Greg KH wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's ridiculous.
I'm with Peter here, why would this be a situation that we should even
support? Are there
On 07/11/2014 01:20 PM, Andi Kleen wrote:
Greg KH gre...@linuxfoundation.org writes:
On Fri, Jul 11, 2014 at 10:29:56AM +0200, Peter Zijlstra wrote:
On Fri, Jul 11, 2014 at 03:37:17PM +0800, Jiang Liu wrote:
Any comments are welcomed!
Why would anybody _ever_ have a memoryless node? That's
38 matches
Mail list logo
