Messages in this thread | | | From | "Zhang, Yanmin" <> | Date | Tue, 19 May 2009 15:15:44 +0800 | Subject | RE: [PATCH 4/4] zone_reclaim_mode is always 0 by default |
| |
>>-----Original Message----- >>From: KOSAKI Motohiro [mailto:kosaki.motohiro@jp.fujitsu.com] >>Sent: 2009年5月19日 15:10 >>To: Zhang, Yanmin >>Cc: kosaki.motohiro@jp.fujitsu.com; Wu, Fengguang; LKML; linux-mm; Andrew >>Morton; Rik van Riel; Christoph Lameter >>Subject: Re: [PATCH 4/4] zone_reclaim_mode is always 0 by default >> >>Hi >> >>> >>> >>Now, it was breaked. What should we do? >>> >>> >>Yanmin, We know 99% linux people use intel cpu and you are one of >>> >>> >>most hard repeated testing >>> >>> [YM] It's very easy to reproduce them on my machines. :) Sometimes, because >>> >>the >>> >>> issues only exist on machines with lots of cpu while other community >>> >>developers >>> >>> have no such environments. >>> >>> >>> >>> >>> >>> guy in lkml and you have much test. >>> >>> >>May I ask your tested machine and benchmark? >>> >>> [YM] Usually I started lots of benchmark testing against the latest >>> >> >>> >>Yeah, that's ok. I and cristoph have. My worries is my unknown workload >>become >>> >>regression. >>> >>so, May I assume you run your benchmark both zonre reclaim 0 and 1 and you >>> >>haven't seen regression by non-zone reclaim mode? >>> [YM] what is non-zone reclaim mode? When zone_reclaim_mode=0? >>> I didn't do that intentionally. Currently I just make sure FIO has a big drop >>> when zone_reclaim_mode=1. I might test it with other benchmarks on 2 Nehalem >>machines. >>
>>May I ask what is FIO? >>File IO? [YM] fio is a tool to test I/O. Jens Axboe is the author.
| |