From: Robin Holt <holt@sgi.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Robin Holt <holt@sgi.com>, LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Christoph Lameter <cl@linux-foundation.org>,
"Zhang, Yanmin" <yanmin.zhang@intel.com>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [PATCH v3] zone_reclaim is always 0 by default
Date: Wed, 27 May 2009 04:50:06 -0500 [thread overview]
Message-ID: <20090527095006.GE29447@sgi.com> (raw)
In-Reply-To: <20090527164549.68B4.A69D9226@jp.fujitsu.com>
On Wed, May 27, 2009 at 05:06:18PM +0900, KOSAKI Motohiro wrote:
> your last patch is one of considerable thing. but it has one weakness.
> in general "ifdef x86" is wrong idea. almost minor architecture don't
> have sufficient tester. the difference against x86 often makes bug.
> Then, unnecessary difference is hated by much people.
Let me start by saying I can barely understand this entire email.
I appreciate that english is a second language for you and you are
doing a service to the linux community with your contributions despite
the language barrier. I commend you for your efforts. I do ask that if
there was more information contained in your email than I am replying too,
please reword it so I may understand.
IIRC, my last patch made it an arch header option to set zone_reclaim_mode
to any value it desired while leaving the default as 1. The only arch
that changed the default was x86 (both 32 and 64 bit). That seems the
least disruptive to existing users.
> So, I think we have two selectable choice.
>
> 1. remove zone_reclaim default setting completely (this patch)
> 2. Only PowerPC and IA64 have default zone_reclaim_mode settings,
> other architecture always use zone_reclaim_mode=0.
Looks like 2 is the inverse of my patch. That is fine as well. The only
reason I formed the patch with the default of 1 and override on x86 is
it was one less line of change and one less file.
Thanks,
Robin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-05-27 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 2:47 KOSAKI Motohiro
2009-05-21 3:27 ` Zhang, Yanmin
2009-05-22 12:26 ` Robin Holt
2009-05-24 13:44 ` KOSAKI Motohiro
2009-05-25 11:41 ` Robin Holt
2009-05-27 8:06 ` KOSAKI Motohiro
2009-05-27 9:50 ` Robin Holt [this message]
2009-05-28 4:30 ` KOSAKI Motohiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090527095006.GE29447@sgi.com \
--to=holt@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=yanmin.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox