linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: + mm-remove-find_max_pfn_with_active_regions.patch added to -mm tree
Date: Mon, 28 Jul 2008 14:24:36 -0700	[thread overview]
Message-ID: <86802c440807281424r73bae246va5e6afc6e2749ea7@mail.gmail.com> (raw)
In-Reply-To: <20080728203959.GA29548@csn.ul.ie>

On Mon, Jul 28, 2008 at 1:40 PM, Mel Gorman <mel@csn.ul.ie> wrote:
> On (28/07/08 13:14), Yinghai Lu didst pronounce:
>> > <SNIP>
>> >
>> > I'm not seeing what different a rename of the parameter will do. Even if
>> > the parameter was renamed, it does not mean current trace information during
>> > memory initialisation needs to be outputted as KERN_INFO which is what this
>> > patch is doing. I am still failing to understand why you want this information
>> > to be generally available.
>>
>> how about KERN_DEBUG?
>>
>> please check
>>
>
> Still NAK due to the noise. Admittedly, I introduced the noise
> in the first place but it was complained about then as well. See
> http://lkml.org/lkml/2006/11/27/124 and later this
> http://lkml.org/lkml/2006/11/27/134 .
>
> At the risk of repeating myself, I am still failing to understand why you want
> this information to be generally available at any loglevel. My expectation is
> that the information is only of relevance when debugging memory initialisation
> problems in which case mminit_loglevel can be used.

ok.
how do think about using meminit_debug to replace minit_loglevel?

YH

--
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>

      parent reply	other threads:[~2008-07-28 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200807280313.m6S3DHDk017400@imap1.linux-foundation.org>
2008-07-28  9:16 ` Mel Gorman
2008-07-28 11:15   ` Yinghai Lu
2008-07-28 11:38     ` Mel Gorman
2008-07-28 18:25       ` Yinghai Lu
2008-07-28 19:15         ` Mel Gorman
2008-07-28 19:38           ` Yinghai Lu
2008-07-28 20:00             ` Mel Gorman
2008-07-28 20:14               ` Yinghai Lu
2008-07-28 20:40                 ` Mel Gorman
2008-07-28 20:55                   ` Andrew Morton
2008-07-28 21:16                     ` Mel Gorman
2008-07-28 21:24                   ` Yinghai Lu [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=86802c440807281424r73bae246va5e6afc6e2749ea7@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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