linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: sekharan@us.ibm.com
Cc: akpm@osdl.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] call mm/page-writeback.c:set_ratelimit() when new pages are hot-added
Date: Mon, 28 Aug 2006 22:08:34 -0700	[thread overview]
Message-ID: <1156828115.5408.34.camel@localhost.localdomain> (raw)
In-Reply-To: <1156803805.1196.74.camel@linuxchandra>

On Mon, 2006-08-28 at 15:23 -0700, Chandra Seetharaman wrote:
> --- linux-2.6.17.orig/mm/memory_hotplug.c
> +++ linux-2.6.17/mm/memory_hotplug.c
> @@ -141,6 +141,7 @@ int online_pages(unsigned long pfn, unsi
>         unsigned long start_pfn;
>         struct zone *zone;
>         int need_zonelists_rebuild = 0;
> +       extern void set_ratelimit(void);
>  
>         /*
>          * This doesn't need a lock to do pfn_to_page().
> @@ -191,6 +192,7 @@ int online_pages(unsigned long pfn, unsi
>         if (need_zonelists_rebuild)
>                 build_all_zonelists();
>         vm_total_pages = nr_free_pagecache_pages();
> +       set_ratelimit();
>         return 0;
>  } 

Hi Chandra,

It would be great if you could put set_ratelimit() into a proper header
like the rest of the functions needed by memory hotplug.  These kinds of
externs are ugly because they can too easily get out of sync with their
definitions and cause problems.

-- 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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-08-29  5:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 22:23 Chandra Seetharaman
2006-08-29  5:08 ` Dave Hansen [this message]
2006-08-29  5:41 ` KAMEZAWA Hiroyuki

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=1156828115.5408.34.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=sekharan@us.ibm.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