From: Rohit Seth <rohit.seth@intel.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Paul Jackson <pj@sgi.com>,
akpm@osdl.org, torvalds@osdl.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Cleanup of __alloc_pages
Date: Tue, 08 Nov 2005 10:17:56 -0800 [thread overview]
Message-ID: <1131473876.2400.9.camel@akash.sc.intel.com> (raw)
In-Reply-To: <43703EFB.1010103@yahoo.com.au>
On Tue, 2005-11-08 at 17:00 +1100, Nick Piggin wrote:
>
> > However, I appreciate your preference to separate cleanup from semantic
> > change. Perhaps this means leaving the ALLOC_CPUSET flag in your
> > cleanup patch, then one of us following on top of that with a patch to
> > simplify and fix the cpuset invocation semantics and a second cleanup
> > patch to remove ALLOC_CPUSET as a separate flag.
> >
>
> That would be good. I'll send off a fresh patch with the
> ALLOC_WATERMARKS fixed after Rohit gets around to looking over
> it.
>
Nick, your changes have really come out good. Thanks. I think it is
definitely a good starting point as it maintains all of existing
behavior.
I guess now I can argue about why we should keep the watermark low for
GFP_HIGH ;-)
Paul, sorry for troubling you with those magic numbers again in the
original patch...
-rohit
WARNING: multiple messages have this Message-ID (diff)
From: Rohit Seth <rohit.seth@intel.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Paul Jackson <pj@sgi.com>,
akpm@osdl.org, torvalds@osdl.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Cleanup of __alloc_pages
Date: Tue, 08 Nov 2005 10:17:56 -0800 [thread overview]
Message-ID: <1131473876.2400.9.camel@akash.sc.intel.com> (raw)
In-Reply-To: <43703EFB.1010103@yahoo.com.au>
On Tue, 2005-11-08 at 17:00 +1100, Nick Piggin wrote:
>
> > However, I appreciate your preference to separate cleanup from semantic
> > change. Perhaps this means leaving the ALLOC_CPUSET flag in your
> > cleanup patch, then one of us following on top of that with a patch to
> > simplify and fix the cpuset invocation semantics and a second cleanup
> > patch to remove ALLOC_CPUSET as a separate flag.
> >
>
> That would be good. I'll send off a fresh patch with the
> ALLOC_WATERMARKS fixed after Rohit gets around to looking over
> it.
>
Nick, your changes have really come out good. Thanks. I think it is
definitely a good starting point as it maintains all of existing
behavior.
I guess now I can argue about why we should keep the watermark low for
GFP_HIGH ;-)
Paul, sorry for troubling you with those magic numbers again in the
original patch...
-rohit
--
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:[~2005-11-08 18:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 1:43 [PATCH]: Cleanup of __alloc_pages Rohit, Seth
2005-11-08 1:43 ` Rohit, Seth
2005-11-08 1:53 ` Andrew Morton
2005-11-08 1:53 ` Andrew Morton
2005-11-08 2:16 ` Rohit Seth
2005-11-08 2:16 ` Rohit Seth
2005-11-08 2:44 ` Andrew Morton
2005-11-08 2:44 ` Andrew Morton
2005-11-08 3:47 ` Nick Piggin
2005-11-08 5:44 ` Paul Jackson
2005-11-08 5:44 ` Paul Jackson
2005-11-08 6:00 ` Nick Piggin
2005-11-08 6:00 ` Nick Piggin
2005-11-08 6:22 ` Paul Jackson
2005-11-08 6:22 ` Paul Jackson
2005-11-08 18:17 ` Rohit Seth [this message]
2005-11-08 18:17 ` Rohit Seth
2005-11-08 19:54 ` Paul Jackson
2005-11-08 19:54 ` Paul Jackson
2005-11-09 2:52 ` Nick Piggin
2005-11-09 2:52 ` Nick Piggin
2005-11-13 5:09 ` Paul Jackson
2005-11-13 5:09 ` Paul Jackson
2005-11-13 5:14 ` Paul Jackson
2005-11-13 5:14 ` Paul Jackson
2005-11-13 7:00 ` Nathan Scott
2005-11-13 7:00 ` Nathan Scott
2005-11-13 7:12 ` Andrew Morton
2005-11-13 7:12 ` Andrew Morton
2005-11-13 7:47 ` Paul Jackson
2005-11-13 7:47 ` Paul Jackson
2005-11-08 3:07 ` Paul Jackson
2005-11-08 3:07 ` Paul Jackson
2005-11-08 5:31 ` Nick Piggin
2005-11-08 5:31 ` Nick Piggin
2005-11-09 0:17 ` Paul Jackson
2005-11-09 0:17 ` Paul Jackson
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=1131473876.2400.9.camel@akash.sc.intel.com \
--to=rohit.seth@intel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.