[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090519115645.4EB7.A69D9226@jp.fujitsu.com>
Date: Tue, 19 May 2009 11:57:38 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc: kosaki.motohiro@...fujitsu.com,
Wu Fengguang <fengguang.wu@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Christoph Lameter <cl@...ux-foundation.org>,
"Zhang, Yanmin" <yanmin.zhang@...el.com>
Subject: Re: [PATCH 4/4] zone_reclaim_mode is always 0 by default
nit fix.
> In general, the feature of workload depended don't fit default option.
> we can't know end-user run what workload anyway.
>
> Fortunately (or Unfortunately), typical workload and machine size had
typical workload and machine size and remote node distance
> significant mutuality.
> Thus, the current default setting calculation had worked well in past days.
>
> 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 guy in lkml and you have much test.
> May I ask your tested machine and benchmark?
>
> if zone_reclaim=0 tendency workload is much than zone_reclaim=1 tendency workload,
> we can drop our afraid and we would prioritize your opinion, of cource.
>
> thanks.
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists