From: Qiang Huang <h.huangqiang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org"
<linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [PATCH] mm, memcg: add a helper function to check may oom condition
Date: Tue, 10 Sep 2013 08:57:03 +0800 [thread overview]
Message-ID: <522E6E5F.7050006@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309091317570.16291-X6Q0R45D7oAcqpCFd4KODRPsWskHk0ljAL8bYrjMMd8@public.gmane.org>
On 2013/9/10 4:22, David Rientjes wrote:
> On Mon, 9 Sep 2013, Qiang Huang wrote:
>
>> diff --git a/include/linux/oom.h b/include/linux/oom.h
>> index da60007..d061c63 100644
>> --- a/include/linux/oom.h
>> +++ b/include/linux/oom.h
>> @@ -82,6 +82,11 @@ static inline void oom_killer_enable(void)
>> oom_killer_disabled = false;
>> }
>>
>> +static inline bool may_oom(gfp_t gfp_mask)
>
> Makes sense, but I think the name should be more specific to gfp flags to
> make it clear what it's using to determine eligibility, maybe oom_gfp_allowed()?
> We usually prefix oom killer functions with "oom".
Yes, oom_gfp_allowed() seems better, I'll send a second version,
thanks for you advice, David.
>
> Nice taste.
>
>> +{
>> + return (gfp_mask & __GFP_FS) && !(gfp_mask & __GFP_NORETRY);
>> +}
>> +
>> extern struct task_struct *find_lock_task_mm(struct task_struct *p);
>>
>> /* sysctls */
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Qiang Huang <h.huangqiang@huawei.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
hannes@cmpxchg.org, Li Zefan <lizefan@huawei.com>,
Cgroups <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm, memcg: add a helper function to check may oom condition
Date: Tue, 10 Sep 2013 08:57:03 +0800 [thread overview]
Message-ID: <522E6E5F.7050006@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309091317570.16291@chino.kir.corp.google.com>
On 2013/9/10 4:22, David Rientjes wrote:
> On Mon, 9 Sep 2013, Qiang Huang wrote:
>
>> diff --git a/include/linux/oom.h b/include/linux/oom.h
>> index da60007..d061c63 100644
>> --- a/include/linux/oom.h
>> +++ b/include/linux/oom.h
>> @@ -82,6 +82,11 @@ static inline void oom_killer_enable(void)
>> oom_killer_disabled = false;
>> }
>>
>> +static inline bool may_oom(gfp_t gfp_mask)
>
> Makes sense, but I think the name should be more specific to gfp flags to
> make it clear what it's using to determine eligibility, maybe oom_gfp_allowed()?
> We usually prefix oom killer functions with "oom".
Yes, oom_gfp_allowed() seems better, I'll send a second version,
thanks for you advice, David.
>
> Nice taste.
>
>> +{
>> + return (gfp_mask & __GFP_FS) && !(gfp_mask & __GFP_NORETRY);
>> +}
>> +
>> extern struct task_struct *find_lock_task_mm(struct task_struct *p);
>>
>> /* sysctls */
>
>
--
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:[~2013-09-10 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 2:18 [PATCH] mm, memcg: add a helper function to check may oom condition Qiang Huang
2013-09-09 2:18 ` Qiang Huang
[not found] ` <522D2FE5.3080606-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-09-09 20:22 ` David Rientjes
2013-09-09 20:22 ` David Rientjes
[not found] ` <alpine.DEB.2.02.1309091317570.16291-X6Q0R45D7oAcqpCFd4KODRPsWskHk0ljAL8bYrjMMd8@public.gmane.org>
2013-09-10 0:57 ` Qiang Huang [this message]
2013-09-10 0:57 ` Qiang Huang
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=522E6E5F.7050006@huawei.com \
--to=h.huangqiang-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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.