Re: Suspicious error for CMA stress test

2016-03-23 17:26 GMT+09:00 Vlastimil Babka : > On 03/23/2016 05:44 AM, Joonsoo Kim wrote: >>> >>> >>> Fixes: 3c605096d315 ("mm/page_alloc: restrict max order of merging on >>> isolated pageblock") >>> Link: https://lkml.org/lkml/2016/3/2/280 >>> Reported-by: Hanjun Guo

Re: Suspicious error for CMA stress test

2016-03-23 17:26 GMT+09:00 Vlastimil Babka : > On 03/23/2016 05:44 AM, Joonsoo Kim wrote: >>> >>> >>> Fixes: 3c605096d315 ("mm/page_alloc: restrict max order of merging on >>> isolated pageblock") >>> Link: https://lkml.org/lkml/2016/3/2/280 >>> Reported-by: Hanjun Guo >>> Debugged-by: Laura

Re: Suspicious error for CMA stress test

On 03/23/2016 05:44 AM, Joonsoo Kim wrote: Fixes: 3c605096d315 ("mm/page_alloc: restrict max order of merging on isolated pageblock") Link: https://lkml.org/lkml/2016/3/2/280 Reported-by: Hanjun Guo Debugged-by: Laura Abbott Debugged-by: Joonsoo Kim

Re: Suspicious error for CMA stress test

On 03/23/2016 05:44 AM, Joonsoo Kim wrote: Fixes: 3c605096d315 ("mm/page_alloc: restrict max order of merging on isolated pageblock") Link: https://lkml.org/lkml/2016/3/2/280 Reported-by: Hanjun Guo Debugged-by: Laura Abbott Debugged-by: Joonsoo Kim Signed-off-by: Vlastimil Babka Cc: #

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 03:10:09PM +0100, Vlastimil Babka wrote: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> Okay. I used following slightly optimized version and I need to > >> add 'max_order = min_t(unsigned

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 03:10:09PM +0100, Vlastimil Babka wrote: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> Okay. I used following slightly optimized version and I need to > >> add 'max_order = min_t(unsigned int, MAX_ORDER,

Re: Suspicious error for CMA stress test

On Tue, Mar 22, 2016 at 03:56:46PM +0100, Lucas Stach wrote: > Am Montag, den 21.03.2016, 13:42 +0900 schrieb Joonsoo Kim: > > On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > > > Hi Vlastimil, Joonsoo, > > > > > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > > >

Re: Suspicious error for CMA stress test

On Tue, Mar 22, 2016 at 03:56:46PM +0100, Lucas Stach wrote: > Am Montag, den 21.03.2016, 13:42 +0900 schrieb Joonsoo Kim: > > On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > > > Hi Vlastimil, Joonsoo, > > > > > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > > >

Re: Suspicious error for CMA stress test

Am Montag, den 21.03.2016, 13:42 +0900 schrieb Joonsoo Kim: > On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > > Hi Vlastimil, Joonsoo, > > > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > > > On

Re: Suspicious error for CMA stress test

Am Montag, den 21.03.2016, 13:42 +0900 schrieb Joonsoo Kim: > On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > > Hi Vlastimil, Joonsoo, > > > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > > > On 03/17/2016 10:24

Re: Suspicious error for CMA stress test

Am Freitag, den 18.03.2016, 21:58 +0100 schrieb Vlastimil Babka: > On 03/18/2016 03:42 PM, Lucas Stach wrote: > > Am Freitag, den 18.03.2016, 15:10 +0100 schrieb Vlastimil Babka: > >> On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > >> > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >>

Re: Suspicious error for CMA stress test

Am Freitag, den 18.03.2016, 21:58 +0100 schrieb Vlastimil Babka: > On 03/18/2016 03:42 PM, Lucas Stach wrote: > > Am Freitag, den 18.03.2016, 15:10 +0100 schrieb Vlastimil Babka: > >> On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > >> > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> OK, here

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > Hi Vlastimil, Joonsoo, > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > > On 03/17/2016 10:24 AM, Hanjun Guo wrote: > > >> > > >> On 2016/3/17 14:54,

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > Hi Vlastimil, Joonsoo, > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > > On 03/17/2016 10:24 AM, Hanjun Guo wrote: > > >> > > >> On 2016/3/17 14:54, Joonsoo Kim

Re: Suspicious error for CMA stress test

On 03/17/2016 07:54 AM, Joonsoo Kim wrote: On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: Hmm, this one is not work, I still can see the bug is there after applying this patch, did I miss something? I may find that there is a bug which was

Re: Suspicious error for CMA stress test

On 03/17/2016 07:54 AM, Joonsoo Kim wrote: On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: Hmm, this one is not work, I still can see the bug is there after applying this patch, did I miss something? I may find that there is a bug which was

Re: Suspicious error for CMA stress test

2016-03-17 18:24 GMT+09:00 Hanjun Guo : > On 2016/3/17 14:54, Joonsoo Kim wrote: >> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: >>> On 2016/3/14 15:18, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > On 03/14/2016

Re: Suspicious error for CMA stress test

2016-03-17 18:24 GMT+09:00 Hanjun Guo : > On 2016/3/17 14:54, Joonsoo Kim wrote: >> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: >>> On 2016/3/14 15:18, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > On 03/14/2016 07:49 AM, Joonsoo Kim

Re: Suspicious error for CMA stress test

Hi Vlastimil, Joonsoo, Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > On 03/17/2016 10:24 AM, Hanjun Guo wrote: > >> > >> On 2016/3/17 14:54, Joonsoo Kim wrote: > >>> > >>> On Wed, Mar 16, 2016 at 05:44:28PM +0800,

Re: Suspicious error for CMA stress test

Hi Vlastimil, Joonsoo, Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > On 03/17/2016 10:24 AM, Hanjun Guo wrote: > >> > >> On 2016/3/17 14:54, Joonsoo Kim wrote: > >>> > >>> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote:

Re: Suspicious error for CMA stress test

Am Freitag, den 18.03.2016, 15:10 +0100 schrieb Vlastimil Babka: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> Okay. I used following slightly optimized version and I need to > >> add 'max_order = min_t(unsigned

Re: Suspicious error for CMA stress test

Am Freitag, den 18.03.2016, 15:10 +0100 schrieb Vlastimil Babka: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> Okay. I used following slightly optimized version and I need to > >> add 'max_order = min_t(unsigned int, MAX_ORDER,

Re: Suspicious error for CMA stress test

On 03/19/2016 08:24 AM, Hanjun Guo wrote: On 2016/3/18 22:10, Vlastimil Babka wrote: Oh, ok, will try to send proper patch, once I figure out what to write in the changelog :) Thanks in advance! OK, here it is. Hanjun can you please retest this, as I'm not sure if you had I tested this

Re: Suspicious error for CMA stress test

On 03/19/2016 08:24 AM, Hanjun Guo wrote: On 2016/3/18 22:10, Vlastimil Babka wrote: Oh, ok, will try to send proper patch, once I figure out what to write in the changelog :) Thanks in advance! OK, here it is. Hanjun can you please retest this, as I'm not sure if you had I tested this

Re: Suspicious error for CMA stress test

On 03/17/2016 10:24 AM, Hanjun Guo wrote: On 2016/3/17 14:54, Joonsoo Kim wrote: On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On

Re: Suspicious error for CMA stress test

On 03/17/2016 10:24 AM, Hanjun Guo wrote: On 2016/3/17 14:54, Joonsoo Kim wrote: On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On

Re: Suspicious error for CMA stress test

On 03/18/2016 03:42 PM, Lucas Stach wrote: Am Freitag, den 18.03.2016, 15:10 +0100 schrieb Vlastimil Babka: On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : OK, here it is. Hanjun can you please retest this, as I'm not sure if you had the

Re: Suspicious error for CMA stress test

On 03/18/2016 03:42 PM, Lucas Stach wrote: Am Freitag, den 18.03.2016, 15:10 +0100 schrieb Vlastimil Babka: On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : OK, here it is. Hanjun can you please retest this, as I'm not sure if you had the same code due

Re: Suspicious error for CMA stress test

2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > On 03/17/2016 10:24 AM, Hanjun Guo wrote: >> >> On 2016/3/17 14:54, Joonsoo Kim wrote: >>> >>> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: > > On Mon, Mar 14, 2016

Re: Suspicious error for CMA stress test

2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > On 03/17/2016 10:24 AM, Hanjun Guo wrote: >> >> On 2016/3/17 14:54, Joonsoo Kim wrote: >>> >>> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: > > On Mon, Mar 14, 2016 at 08:06:16AM

Re: Suspicious error for CMA stress test

On 2016/3/17 14:54, Joonsoo Kim wrote: > On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: >> On 2016/3/14 15:18, Joonsoo Kim wrote: >>> On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: On 03/14/2016 07:49 AM, Joonsoo Kim wrote: > On Fri, Mar 11, 2016 at

Re: Suspicious error for CMA stress test

On 2016/3/17 14:54, Joonsoo Kim wrote: > On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: >> On 2016/3/14 15:18, Joonsoo Kim wrote: >>> On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: On 03/14/2016 07:49 AM, Joonsoo Kim wrote: > On Fri, Mar 11, 2016 at

Re: Suspicious error for CMA stress test

On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: > On 2016/3/14 15:18, Joonsoo Kim wrote: > > On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > >> On 03/14/2016 07:49 AM, Joonsoo Kim wrote: > >>> On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > On

Re: Suspicious error for CMA stress test

On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: > On 2016/3/14 15:18, Joonsoo Kim wrote: > > On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > >> On 03/14/2016 07:49 AM, Joonsoo Kim wrote: > >>> On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > On

Re: Suspicious error for CMA stress test

On 2016/3/17 23:31, Joonsoo Kim wrote: [...] >>> I may find that there is a bug which was introduced by me some time >>> ago. Could you test following change in __free_one_page() on top of >>> Vlastimil's patch? >>> >>> -page_idx = pfn & ((1 << max_order) - 1); >>> +page_idx = pfn & ((1 <<

Re: Suspicious error for CMA stress test

On 2016/3/17 23:31, Joonsoo Kim wrote: [...] >>> I may find that there is a bug which was introduced by me some time >>> ago. Could you test following change in __free_one_page() on top of >>> Vlastimil's patch? >>> >>> -page_idx = pfn & ((1 << max_order) - 1); >>> +page_idx = pfn & ((1 <<

Re: Suspicious error for CMA stress test

On 2016/3/18 22:10, Vlastimil Babka wrote: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: >> 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : >>> Okay. I used following slightly optimized version and I need to >>> add 'max_order = min_t(unsigned int, MAX_ORDER, pageblock_order +

Re: Suspicious error for CMA stress test

On 2016/3/18 22:10, Vlastimil Babka wrote: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: >> 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : >>> Okay. I used following slightly optimized version and I need to >>> add 'max_order = min_t(unsigned int, MAX_ORDER, pageblock_order + 1)' >>> to

Re: Suspicious error for CMA stress test

On 03/14/2016 03:10 PM, Joonsoo Kim wrote: 2016-03-14 21:30 GMT+09:00 Vlastimil Babka : Now I see why this happen. I enabled CONFIG_DEBUG_PAGEALLOC and it makes difference. I tested on x86_64, gcc (Ubuntu 4.8.4-2ubuntu1~14.04.1) 4.8.4. With CONFIG_CMA + CONFIG_DEBUG_PAGEALLOC

Re: Suspicious error for CMA stress test

On 03/14/2016 03:10 PM, Joonsoo Kim wrote: 2016-03-14 21:30 GMT+09:00 Vlastimil Babka : Now I see why this happen. I enabled CONFIG_DEBUG_PAGEALLOC and it makes difference. I tested on x86_64, gcc (Ubuntu 4.8.4-2ubuntu1~14.04.1) 4.8.4. With CONFIG_CMA + CONFIG_DEBUG_PAGEALLOC

Re: Suspicious error for CMA stress test

On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : >> >> Okay. I used following slightly optimized version and I need to >> add 'max_order = min_t(unsigned int, MAX_ORDER, pageblock_order + 1)' >> to yours. Please consider it,

Re: Suspicious error for CMA stress test

On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : >> >> Okay. I used following slightly optimized version and I need to >> add 'max_order = min_t(unsigned int, MAX_ORDER, pageblock_order + 1)' >> to yours. Please consider it, too. > >

Re: Suspicious error for CMA stress test

On 2016/3/14 15:18, Joonsoo Kim wrote: > On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: >> On 03/14/2016 07:49 AM, Joonsoo Kim wrote: >>> On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: On 03/11/2016 04:00 PM, Joonsoo Kim wrote: How about something

Re: Suspicious error for CMA stress test

On 2016/3/14 15:18, Joonsoo Kim wrote: > On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: >> On 03/14/2016 07:49 AM, Joonsoo Kim wrote: >>> On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: On 03/11/2016 04:00 PM, Joonsoo Kim wrote: How about something

Re: Suspicious error for CMA stress test

2016-03-14 21:30 GMT+09:00 Vlastimil Babka : > On 03/14/2016 08:18 AM, Joonsoo Kim wrote: >> >> On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: >>> >>> On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka

Re: Suspicious error for CMA stress test

2016-03-14 21:30 GMT+09:00 Vlastimil Babka : > On 03/14/2016 08:18 AM, Joonsoo Kim wrote: >> >> On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: >>> >>> On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > >

Re: Suspicious error for CMA stress test

On 03/14/2016 08:18 AM, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: On 03/11/2016 04:00 PM, Joonsoo Kim wrote: How about something like this?

Re: Suspicious error for CMA stress test

On 03/14/2016 08:18 AM, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: On 03/11/2016 04:00 PM, Joonsoo Kim wrote: How about something like this?

Re: Suspicious error for CMA stress test

On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > On 03/14/2016 07:49 AM, Joonsoo Kim wrote: > >On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > >>On 03/11/2016 04:00 PM, Joonsoo Kim wrote: > >> > >>How about something like this? Just and idea, probably buggy

Re: Suspicious error for CMA stress test

On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > On 03/14/2016 07:49 AM, Joonsoo Kim wrote: > >On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > >>On 03/11/2016 04:00 PM, Joonsoo Kim wrote: > >> > >>How about something like this? Just and idea, probably buggy

Re: Suspicious error for CMA stress test

On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: On 03/11/2016 04:00 PM, Joonsoo Kim wrote: How about something like this? Just and idea, probably buggy (off-by-one etc.). Should keep away cost from pageblock_order iterations. Hmm...

Re: Suspicious error for CMA stress test

On 03/14/2016 07:49 AM, Joonsoo Kim wrote: On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: On 03/11/2016 04:00 PM, Joonsoo Kim wrote: How about something like this? Just and idea, probably buggy (off-by-one etc.). Should keep away cost from pageblock_order iterations. Hmm...

Re: Suspicious error for CMA stress test

On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > On 03/11/2016 04:00 PM, Joonsoo Kim wrote: > > 2016-03-09 10:23 GMT+09:00 Leizhen (ThunderTown) > > : > >> > >> Hi, Joonsoo: > >> This new patch worked well. Do you plan to upstream it in the

Re: Suspicious error for CMA stress test

On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote: > On 03/11/2016 04:00 PM, Joonsoo Kim wrote: > > 2016-03-09 10:23 GMT+09:00 Leizhen (ThunderTown) > > : > >> > >> Hi, Joonsoo: > >> This new patch worked well. Do you plan to upstream it in the near > >> furture? > > > >

Re: Suspicious error for CMA stress test

On 03/11/2016 04:00 PM, Joonsoo Kim wrote: > 2016-03-09 10:23 GMT+09:00 Leizhen (ThunderTown) : >> >> Hi, Joonsoo: >> This new patch worked well. Do you plan to upstream it in the near >> furture? > > Of course! > But, I should think more because it touches

Re: Suspicious error for CMA stress test

On 03/11/2016 04:00 PM, Joonsoo Kim wrote: > 2016-03-09 10:23 GMT+09:00 Leizhen (ThunderTown) : >> >> Hi, Joonsoo: >> This new patch worked well. Do you plan to upstream it in the near >> furture? > > Of course! > But, I should think more because it touches allocator's fastpatch and >

Re: Suspicious error for CMA stress test

;>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>>>>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott <labb...@redhat.com>: >>>>>>>>>>>>> (cc -mm and Joonsoo Kim) >>>>>>>>&g

Re: Suspicious error for CMA stress test

t;> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>>>>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : >>>>>>>>>>>>> (cc -mm and Joonsoo Kim) >>>>>>>>>>>>> >>>&

Re: Suspicious error for CMA stress test

On 2016/3/8 23:36, Joonsoo Kim wrote: > 2016-03-08 19:45 GMT+09:00 Xishi Qiu : >> On 2016/3/8 15:48, Joonsoo Kim wrote: >> >>> On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: On 03/07/2016 05:34 AM, Joonsoo Kim wrote: > On Fri, Mar 04, 2016 at

Re: Suspicious error for CMA stress test

On 2016/3/8 23:36, Joonsoo Kim wrote: > 2016-03-08 19:45 GMT+09:00 Xishi Qiu : >> On 2016/3/8 15:48, Joonsoo Kim wrote: >> >>> On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: On 03/07/2016 05:34 AM, Joonsoo Kim wrote: > On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun

Re: Suspicious error for CMA stress test

02:33AM +0900, Joonsoo Kim wrote: >>>>>>>>> On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: >>>>>>>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>>>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott <labb...@

Re: Suspicious error for CMA stress test

02:33AM +0900, Joonsoo Kim wrote: >>>>>>>>> On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: >>>>>>>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>>>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbo

Re: Suspicious error for CMA stress test

2016-03-08 19:45 GMT+09:00 Xishi Qiu : > On 2016/3/8 15:48, Joonsoo Kim wrote: > >> On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: >>> On 03/07/2016 05:34 AM, Joonsoo Kim wrote: On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: >> Sad to

Re: Suspicious error for CMA stress test

2016-03-08 19:45 GMT+09:00 Xishi Qiu : > On 2016/3/8 15:48, Joonsoo Kim wrote: > >> On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: >>> On 03/07/2016 05:34 AM, Joonsoo Kim wrote: On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: >> Sad to hear that. >>

Re: Suspicious error for CMA stress test

On 2016/3/8 15:48, Joonsoo Kim wrote: > On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: >> On 03/07/2016 05:34 AM, Joonsoo Kim wrote: >>> On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: > Sad to hear that. > > Could you tell me your system's MAX_ORDER and

Re: Suspicious error for CMA stress test

On 2016/3/8 15:48, Joonsoo Kim wrote: > On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: >> On 03/07/2016 05:34 AM, Joonsoo Kim wrote: >>> On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: > Sad to hear that. > > Could you tell me your system's MAX_ORDER and

Re: Suspicious error for CMA stress test

2, Joonsoo Kim wrote: > >>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott <labb...@redhat.com>: > >>>>> (cc -mm and Joonsoo Kim) > >>>>> > >>>>> > >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>&

Re: Suspicious error for CMA stress test

2, Joonsoo Kim wrote: > >>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : > >>>>> (cc -mm and Joonsoo Kim) > >>>>> > >>>>> > >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>>> Hi, > >

Re: Suspicious error for CMA stress test

On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: > On 03/07/2016 05:34 AM, Joonsoo Kim wrote: > >On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: > >>>Sad to hear that. > >>> > >>>Could you tell me your system's MAX_ORDER and pageblock_order? > >>> > >> > >>MAX_ORDER is

Re: Suspicious error for CMA stress test

On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote: > On 03/07/2016 05:34 AM, Joonsoo Kim wrote: > >On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: > >>>Sad to hear that. > >>> > >>>Could you tell me your system's MAX_ORDER and pageblock_order? > >>> > >> > >>MAX_ORDER is

Re: Suspicious error for CMA stress test

Hi, I came across a suspicious error for CMA stress test: Before the test, I got: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 195044 kB After running the test: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 6602584

Re: Suspicious error for CMA stress test

a suspicious error for CMA stress test: Before the test, I got: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 195044 kB After running the test: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 6602584 kB So the freed CMA memory

Re: Suspicious error for CMA stress test

00, Hanjun Guo wrote: >>>>>>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott <labb...@redhat.com>: >>>>>>>>>>> (cc -mm and Joonsoo Kim) >>

Re: Suspicious error for CMA stress test

00, Hanjun Guo wrote: >>>>>>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : >>>>>>>>>>> (cc -mm and Joonsoo Kim) >>>>>>>>>>> >

Re: Suspicious error for CMA stress test

hat.com>: >>>>> (cc -mm and Joonsoo Kim) >>>>> >>>>> >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>> Hi, >>>>>> >>>>>> I came across a suspicious error for CMA stress test

Re: Suspicious error for CMA stress test

bott : >>>>> (cc -mm and Joonsoo Kim) >>>>> >>>>> >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>> Hi, >>>>>> >>>>>> I came across a suspicious error for CMA stress test: >>>>>> >&g

Re: Suspicious error for CMA stress test

Hi, I came across a suspicious error for CMA stress test: Before the test, I got: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 195044 kB After running the test: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 6602584

Re: Suspicious error for CMA stress test

a suspicious error for CMA stress test: Before the test, I got: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 195044 kB After running the test: -bash-4.3# cat /proc/meminfo | grep Cma CmaTotal: 204800 kB CmaFree: 6602584 kB So the freed CMA memory

Re: Suspicious error for CMA stress test

On 03/07/2016 05:34 AM, Joonsoo Kim wrote: On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: Sad to hear that. Could you tell me your system's MAX_ORDER and pageblock_order? MAX_ORDER is 11, pageblock_order is 9, thanks for your help! I thought that CMA regions/operations (and

Re: Suspicious error for CMA stress test

On 03/07/2016 05:34 AM, Joonsoo Kim wrote: On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote: Sad to hear that. Could you tell me your system's MAX_ORDER and pageblock_order? MAX_ORDER is 11, pageblock_order is 9, thanks for your help! I thought that CMA regions/operations (and

Re: Suspicious error for CMA stress test

..@redhat.com>: >>>>>>>>> (cc -mm and Joonsoo Kim) >>>>>>>>> >>>>>>>>> >>>>>>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>>>>>> Hi

Re: Suspicious error for CMA stress test

: >>>>>>>>> (cc -mm and Joonsoo Kim) >>>>>>>>> >>>>>>>>> >>>>>>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>>>>>> Hi, >>>>>>>>>> &g

Re: Suspicious error for CMA stress test

bb...@redhat.com>: > >>>> (cc -mm and Joonsoo Kim) > >>>> > >>>> > >>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>> Hi, > >>>>> > >>>>> I came across a suspicious error for CMA st

Re: Suspicious error for CMA stress test

> >>>> (cc -mm and Joonsoo Kim) > >>>> > >>>> > >>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>> Hi, > >>>>> > >>>>> I came across a suspicious error for CMA stress test: > >>&g

Re: Suspicious error for CMA stress test

gt; (cc -mm and Joonsoo Kim) > >>>>>>> > >>>>>>> > >>>>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> I came across a s

Re: Suspicious error for CMA stress test

gt;>>>> > >>>>>>> > >>>>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> I came across a suspicious error for CMA stress te

Re: Suspicious error for CMA stress test

wrote: >>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott <labb...@redhat.com>: >>>>>>> (cc -mm and Joonsoo Kim) >>>>>>> >>>>>>> >>>>>>>

Re: Suspicious error for CMA stress test

wrote: >>>>> On 2016/3/3 15:42, Joonsoo Kim wrote: >>>>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : >>>>>>> (cc -mm and Joonsoo Kim) >>>>>>> >>>>>>> >>>>>>> On 03/02/2016 05:52

Re: Suspicious error for CMA stress test

t;>>> >>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>> Hi, >>>>> >>>>> I came across a suspicious error for CMA stress test: >>>>> >>>>> Before the test, I got: >>>>> -bash-4.3# cat /proc/m

Re: Suspicious error for CMA stress test

On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>> Hi, >>>>> >>>>> I came across a suspicious error for CMA stress test: >>>>> >>>>> Before the test, I got: >>>>> -bash-4.3# cat /proc/meminfo | grep Cma

Re: Suspicious error for CMA stress test

wrote: > >>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott <labb...@redhat.com>: > >>>>> (cc -mm and Joonsoo Kim) > >>>>> > >>>>> > >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>>> Hi,

Re: Suspicious error for CMA stress test

wrote: > >>>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : > >>>>> (cc -mm and Joonsoo Kim) > >>>>> > >>>>> > >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > >>>>>> Hi, > >>>>>

Re: Suspicious error for CMA stress test

m>: >>>>> (cc -mm and Joonsoo Kim) >>>>> >>>>> >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>> Hi, >>>>>> >>>>>> I came across a suspicious error for CMA stress test: >

Re: Suspicious error for CMA stress test

Joonsoo Kim) >>>>> >>>>> >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>> Hi, >>>>>> >>>>>> I came across a suspicious error for CMA stress test: >>>>>> >>>>>

Re: Suspicious error for CMA stress test

t.com>: >>>>> (cc -mm and Joonsoo Kim) >>>>> >>>>> >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>> Hi, >>>>>> >>>>>> I came across a suspicious error for CMA stress test: >

Re: Suspicious error for CMA stress test

>>>>> (cc -mm and Joonsoo Kim) >>>>> >>>>> >>>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>>> Hi, >>>>>> >>>>>> I came across a suspicious error for CMA stress test: >>&g

Re: Suspicious error for CMA stress test

gt;> >>>> >>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>> Hi, >>>>> >>>>> I came across a suspicious error for CMA stress test: >>>>> >>>>> Before the test, I got: >>>>> -bash-4.

Re: Suspicious error for CMA stress test

gt;>>> On 03/02/2016 05:52 AM, Hanjun Guo wrote: >>>>> Hi, >>>>> >>>>> I came across a suspicious error for CMA stress test: >>>>> >>>>> Before the test, I got: >>>>> -bash-4.3# cat /proc/meminfo | grep

Re: Suspicious error for CMA stress test

o Kim) > > >> > > >> > > >> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > > >>> Hi, > > >>> > > >>> I came across a suspicious error for CMA stress test: > > >>> > > >>&

Re: Suspicious error for CMA stress test

t; > >> > > >> On 03/02/2016 05:52 AM, Hanjun Guo wrote: > > >>> Hi, > > >>> > > >>> I came across a suspicious error for CMA stress test: > > >>> > > >>> Before the test, I got: > > >>> -b

  1   2   >