From: Dave Hansen <haveblue@us.ibm.com>
To: "Chandra S. Seetharaman [imap]" <sekharan@us.ibm.com>
Cc: YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
ckrm-tech@lists.sourceforge.net, linux-mm <linux-mm@kvack.org>
Subject: Re: [ckrm-tech] [PATCH 4/6] CKRM: Add guarantee support for mem controller
Date: Thu, 30 Jun 2005 12:29:37 -0700 [thread overview]
Message-ID: <1120159777.12143.74.camel@localhost> (raw)
In-Reply-To: <1120159282.14910.60.camel@linuxchandra>
On Thu, 2005-06-30 at 12:21 -0700, Chandra Seetharaman wrote:
> Hmm.... either you are looking at a old set of patches or you do not
> have all the patches in the current set. ckrm_clear_page_class is _not_
> from free_pages_bulk in the current patchset fully applied :).
I was looking at the patches individually.
> chandra
> PS: it should not be there in any of the patches in the current
> patchset, but is left out due to code rearrangements, I will fix that.
I find the whole patch set really hard to understand. It seems more
like a linear set of how you wrote it and fixed it, rather than broken
up into logical components.
For instance, what does "Add guarantee support for mem-controller" have
to do with removing ckrm_clear_page_class() from the allocator path?
If there was a reason that you remove that function from
__free_pages_bulk(), because of a bug fix, it needs to go into a
separate patch.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2005-06-30 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 22:25 Chandra Seetharaman
2005-06-30 5:52 ` [ckrm-tech] " YAMAMOTO Takashi
2005-06-30 18:11 ` Chandra Seetharaman
2005-06-30 18:23 ` Dave Hansen
2005-06-30 18:53 ` Chandra Seetharaman
2005-06-30 19:02 ` Dave Hansen
2005-06-30 19:21 ` Chandra Seetharaman
2005-06-30 19:29 ` Dave Hansen [this message]
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=1120159777.12143.74.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=sekharan@us.ibm.com \
--cc=yamamoto@valinux.co.jp \
/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