On 01/16/2017 02:22 PM, Vlastimil Babka wrote:
>>>
>>> no_zone:
>>> --
>>> 2.11.0
>>>
>>
>> this patch did not fix the issue.
>> issue still exists!
>
> Hmm, that's unfortunate.
>
>> i did bisect and this test passes in 4.4,4.5 and 4.6
>> test failing since 4.7-rc1
>
> 4.7 would match the
On 01/16/2017 02:22 PM, Vlastimil Babka wrote:
>>>
>>> no_zone:
>>> --
>>> 2.11.0
>>>
>>
>> this patch did not fix the issue.
>> issue still exists!
>
> Hmm, that's unfortunate.
>
>> i did bisect and this test passes in 4.4,4.5 and 4.6
>> test failing since 4.7-rc1
>
> 4.7 would match the
On 01/16/2017 11:41 AM, Ganapatrao Kulkarni wrote:
> On Fri, Jan 13, 2017 at 2:36 PM, Vlastimil Babka wrote:
>> On 01/13/2017 05:35 AM, Ganapatrao Kulkarni wrote:
>>> On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
On 01/11/2017 05:46 PM, Michal Hocko
On 01/16/2017 11:41 AM, Ganapatrao Kulkarni wrote:
> On Fri, Jan 13, 2017 at 2:36 PM, Vlastimil Babka wrote:
>> On 01/13/2017 05:35 AM, Ganapatrao Kulkarni wrote:
>>> On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
On 01/11/2017 05:46 PM, Michal Hocko wrote:
>
> On Wed
On Fri, Jan 13, 2017 at 2:36 PM, Vlastimil Babka wrote:
> On 01/13/2017 05:35 AM, Ganapatrao Kulkarni wrote:
>> On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
>>> On 01/11/2017 05:46 PM, Michal Hocko wrote:
On Wed 11-01-17 21:52:29, Ganapatrao
On Fri, Jan 13, 2017 at 2:36 PM, Vlastimil Babka wrote:
> On 01/13/2017 05:35 AM, Ganapatrao Kulkarni wrote:
>> On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
>>> On 01/11/2017 05:46 PM, Michal Hocko wrote:
On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
> [
On Fri 13-01-17 10:06:14, Vlastimil Babka wrote:
[...]
> >From 9f041839401681f2678edf5040c851d11963c5fe Mon Sep 17 00:00:00 2001
> From: Vlastimil Babka
> Date: Fri, 13 Jan 2017 10:01:26 +0100
> Subject: [PATCH] mm, page_alloc: fix race with cpuset update or removal
>
> Changelog
On Fri 13-01-17 10:06:14, Vlastimil Babka wrote:
[...]
> >From 9f041839401681f2678edf5040c851d11963c5fe Mon Sep 17 00:00:00 2001
> From: Vlastimil Babka
> Date: Fri, 13 Jan 2017 10:01:26 +0100
> Subject: [PATCH] mm, page_alloc: fix race with cpuset update or removal
>
> Changelog and S-O-B TBD.
On 01/13/2017 05:35 AM, Ganapatrao Kulkarni wrote:
> On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
>> On 01/11/2017 05:46 PM, Michal Hocko wrote:
>>>
>>> On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
>>>
[ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB
On 01/13/2017 05:35 AM, Ganapatrao Kulkarni wrote:
> On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
>> On 01/11/2017 05:46 PM, Michal Hocko wrote:
>>>
>>> On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
>>>
[ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB (UME) 1034*16kB
On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
> On 01/11/2017 05:46 PM, Michal Hocko wrote:
>>
>> On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
>>
>>> [ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB (UME) 1034*16kB
>>> (UME) 742*32kB (UME) 581*64kB (UME)
On Thu, Jan 12, 2017 at 4:40 PM, Vlastimil Babka wrote:
> On 01/11/2017 05:46 PM, Michal Hocko wrote:
>>
>> On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
>>
>>> [ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB (UME) 1034*16kB
>>> (UME) 742*32kB (UME) 581*64kB (UME) 450*128kB (UME)
On 01/11/2017 05:46 PM, Michal Hocko wrote:
On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
[ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB (UME) 1034*16kB (UME)
742*32kB (UME) 581*64kB (UME) 450*128kB (UME) 362*256kB (UME) 275*512kB (ME)
189*1024kB (UM) 117*2048kB (ME) 2742*4096kB
On 01/11/2017 05:46 PM, Michal Hocko wrote:
On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
[ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB (UME) 1034*16kB (UME)
742*32kB (UME) 581*64kB (UME) 450*128kB (UME) 362*256kB (UME) 275*512kB (ME)
189*1024kB (UM) 117*2048kB (ME) 2742*4096kB
On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
[...]
> [ 2397.331098] cpuset01 invoked oom-killer:
> gfp_mask=0x24280ca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), nodemask=1, order=0,
> oom_score_adj=0
> [ 2397.331100] cpuset01 cpuset=1 mems_allowed=1
[...]
> [ 2397.331206] Node 1
On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
[...]
> [ 2397.331098] cpuset01 invoked oom-killer:
> gfp_mask=0x24280ca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), nodemask=1, order=0,
> oom_score_adj=0
> [ 2397.331100] cpuset01 cpuset=1 mems_allowed=1
[...]
> [ 2397.331206] Node 1
On Wed 11-01-17 12:05:44, Vlastimil Babka wrote:
> On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
> > Hi,
> >
> > we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> > 360) test for few minutes, even through the numa system has adequate
> > memory on both nodes.
> >
> >
On Wed 11-01-17 12:05:44, Vlastimil Babka wrote:
> On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
> > Hi,
> >
> > we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> > 360) test for few minutes, even through the numa system has adequate
> > memory on both nodes.
> >
> >
On Wed 11-01-17 16:20:45, Ganapatrao Kulkarni wrote:
> Hi,
>
> we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> 360) test for few minutes, even through the numa system has adequate
> memory on both nodes.
>
> this we have observed same on both arm64/thunderx numa and on
On Wed 11-01-17 16:20:45, Ganapatrao Kulkarni wrote:
> Hi,
>
> we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> 360) test for few minutes, even through the numa system has adequate
> memory on both nodes.
>
> this we have observed same on both arm64/thunderx numa and on
On 01/11/2017 12:05 PM, Vlastimil Babka wrote:
> On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
>> Hi,
>>
>> we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
>> 360) test for few minutes, even through the numa system has adequate
>> memory on both nodes.
>>
>> this we
On 01/11/2017 12:05 PM, Vlastimil Babka wrote:
> On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
>> Hi,
>>
>> we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
>> 360) test for few minutes, even through the numa system has adequate
>> memory on both nodes.
>>
>> this we
On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
> Hi,
>
> we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> 360) test for few minutes, even through the numa system has adequate
> memory on both nodes.
>
> this we have observed same on both arm64/thunderx numa and on x86
On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
> Hi,
>
> we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> 360) test for few minutes, even through the numa system has adequate
> memory on both nodes.
>
> this we have observed same on both arm64/thunderx numa and on x86
Hi,
we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
360) test for few minutes, even through the numa system has adequate
memory on both nodes.
this we have observed same on both arm64/thunderx numa and on x86 numa system!
using latest ltp from master branch version
Hi,
we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
360) test for few minutes, even through the numa system has adequate
memory on both nodes.
this we have observed same on both arm64/thunderx numa and on x86 numa system!
using latest ltp from master branch version
26 matches
Mail list logo