From: Andrew Morton <akpm@linux-foundation.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com, mhocko@suse.cz
Subject: Re: [PATCH] memcg/hugetlb: Add failcnt support for hugetlb extension
Date: Wed, 23 May 2012 22:16:55 -0700 [thread overview]
Message-ID: <20120523221655.a067710b.akpm@linux-foundation.org> (raw)
In-Reply-To: <87likiyyxr.fsf@skywalker.in.ibm.com>
On Thu, 24 May 2012 10:10:00 +0530 "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> Andrew Morton <akpm@linux-foundation.org> writes:
>
> > On Tue, 22 May 2012 17:13:11 +0530
> > "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> >
> >> Expose the failcnt details to userspace similar to memory and memsw.
> >
> > Why?
> >
>
> to help us find whether there was an allocation failure due to HugeTLB
> limit.
How are we to know that is that useful enough to justify expanding the
kernel API?
Yes, regular memcg has it, but that isn't a reason. Do we know that
people are using that? That it is useful?
Also, "cnt" is not a word. It should be "failcount" or, even better,
"failure_count". Or, smarter, "failures". But we screwed that up a
long time ago and can't fix it.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-24 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 11:43 [PATCH] memcg/hugetlb: Add failcnt support for hugetlb extension Aneesh Kumar K.V
2012-05-23 23:17 ` Andrew Morton
2012-05-24 4:40 ` Aneesh Kumar K.V
2012-05-24 5:16 ` Andrew Morton [this message]
2012-05-24 8:29 ` 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=20120523221655.a067710b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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.