From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com, akpm@linux-foundation.org,
linux-mm@kvack.org
Subject: Re: [PATCH] oom: move oom_killer_enable()/oom_killer_disable to where they belong
Date: Wed, 26 Aug 2009 16:29:33 +0900 (JST) [thread overview]
Message-ID: <20090826162812.3964.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090821191925.GA5367@x200.localdomain>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
Please write proper patch description...
However, I think the code itself is right.
Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>
> include/linux/gfp.h | 12 ------------
> include/linux/oom.h | 11 +++++++++++
> kernel/power/process.c | 1 +
> 3 files changed, 12 insertions(+), 12 deletions(-)
>
> --- a/include/linux/gfp.h
> +++ b/include/linux/gfp.h
> @@ -336,18 +336,6 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
> void drain_all_pages(void);
> void drain_local_pages(void *dummy);
>
> -extern bool oom_killer_disabled;
> -
> -static inline void oom_killer_disable(void)
> -{
> - oom_killer_disabled = true;
> -}
> -
> -static inline void oom_killer_enable(void)
> -{
> - oom_killer_disabled = false;
> -}
> -
> extern gfp_t gfp_allowed_mask;
>
> static inline void set_gfp_allowed_mask(gfp_t mask)
> --- a/include/linux/oom.h
> +++ b/include/linux/oom.h
> @@ -30,5 +30,16 @@ extern void out_of_memory(struct zonelist *zonelist, gfp_t gfp_mask, int order);
> extern int register_oom_notifier(struct notifier_block *nb);
> extern int unregister_oom_notifier(struct notifier_block *nb);
>
> +extern bool oom_killer_disabled;
> +
> +static inline void oom_killer_disable(void)
> +{
> + oom_killer_disabled = true;
> +}
> +
> +static inline void oom_killer_enable(void)
> +{
> + oom_killer_disabled = false;
> +}
> #endif /* __KERNEL__*/
> #endif /* _INCLUDE_LINUX_OOM_H */
> --- a/kernel/power/process.c
> +++ b/kernel/power/process.c
> @@ -9,6 +9,7 @@
> #undef DEBUG
>
> #include <linux/interrupt.h>
> +#include <linux/oom.h>
> #include <linux/suspend.h>
> #include <linux/module.h>
> #include <linux/syscalls.h>
>
> --
> 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>
--
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>
prev parent reply other threads:[~2009-08-26 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 19:19 Alexey Dobriyan
2009-08-21 19:51 ` David Rientjes
2009-08-26 7:29 ` KOSAKI Motohiro [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=20090826162812.3964.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox