From: Pekka Enberg <penberg@kernel.org>
To: Rafael Aquini <aquini@redhat.com>
Cc: David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, Randy Dunlap <rdunlap@xenotime.net>,
Christoph Lameter <cl@linux-foundation.org>,
Matt Mackall <mpm@selenic.com>, Rik van Riel <riel@redhat.com>,
Josef Bacik <josef@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oom: add sysctl to enable slab memory dump
Date: Thu, 23 Feb 2012 18:03:56 +0200 [thread overview]
Message-ID: <1330013036.13624.78.camel@jaguar> (raw)
In-Reply-To: <20120223152226.GA2014@x61.redhat.com>
On Thu, 2012-02-23 at 13:22 -0200, Rafael Aquini wrote:
> > I think this also gives another usecase for a possible /dev/mem_notify in
> > the future: userspace could easily poll on an eventfd and wait for an oom
> > to occur and then cat /proc/slabinfo to attain all this. In other words,
> > if we had this functionality (which I think we undoubtedly will in the
> > future), this patch would be obsoleted.
>
> Great! So, why not letting the time tell us if this feature will be obsoleted
> or not? I'd rather have this patch obsoleted by another one proven better, than
> just stay still waiting for something that might, or might not, happen in the
> future.
Sure.
I'm not really convinced such an ABI would be a full replacement for
this patch. There's certainly advantages to having all this visible in
syslog even if we'd have such a mechanism.
Pekka
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@kernel.org>
To: Rafael Aquini <aquini@redhat.com>
Cc: David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, Randy Dunlap <rdunlap@xenotime.net>,
Christoph Lameter <cl@linux-foundation.org>,
Matt Mackall <mpm@selenic.com>, Rik van Riel <riel@redhat.com>,
Josef Bacik <josef@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oom: add sysctl to enable slab memory dump
Date: Thu, 23 Feb 2012 18:03:56 +0200 [thread overview]
Message-ID: <1330013036.13624.78.camel@jaguar> (raw)
In-Reply-To: <20120223152226.GA2014@x61.redhat.com>
On Thu, 2012-02-23 at 13:22 -0200, Rafael Aquini wrote:
> > I think this also gives another usecase for a possible /dev/mem_notify in
> > the future: userspace could easily poll on an eventfd and wait for an oom
> > to occur and then cat /proc/slabinfo to attain all this. In other words,
> > if we had this functionality (which I think we undoubtedly will in the
> > future), this patch would be obsoleted.
>
> Great! So, why not letting the time tell us if this feature will be obsoleted
> or not? I'd rather have this patch obsoleted by another one proven better, than
> just stay still waiting for something that might, or might not, happen in the
> future.
Sure.
I'm not really convinced such an ABI would be a full replacement for
this patch. There's certainly advantages to having all this visible in
syslog even if we'd have such a mechanism.
Pekka
next prev parent reply other threads:[~2012-02-23 16:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 11:53 [PATCH] oom: add sysctl to enable slab memory dump Rafael Aquini
2012-02-22 11:53 ` Rafael Aquini
2012-02-22 13:17 ` Pekka Enberg
2012-02-22 13:17 ` Pekka Enberg
2012-02-22 16:04 ` Rafael Aquini
2012-02-22 16:04 ` Rafael Aquini
2012-02-22 13:55 ` Christoph Lameter
2012-02-22 13:55 ` Christoph Lameter
2012-02-22 16:14 ` Rafael Aquini
2012-02-22 16:14 ` Rafael Aquini
2012-02-22 16:29 ` Christoph Lameter
2012-02-22 16:29 ` Christoph Lameter
2012-02-23 0:44 ` David Rientjes
2012-02-23 0:44 ` David Rientjes
2012-02-23 15:02 ` Josef Bacik
2012-02-23 15:02 ` Josef Bacik
2012-02-23 23:09 ` David Rientjes
2012-02-23 23:09 ` David Rientjes
2012-02-24 15:10 ` Josef Bacik
2012-02-24 15:10 ` Josef Bacik
2012-02-24 21:45 ` David Rientjes
2012-02-24 21:45 ` David Rientjes
2012-02-24 21:52 ` Pekka Enberg
2012-02-24 21:52 ` Pekka Enberg
2012-02-24 23:51 ` David Rientjes
2012-02-24 23:51 ` David Rientjes
2012-02-23 15:22 ` Rafael Aquini
2012-02-23 15:22 ` Rafael Aquini
2012-02-23 16:03 ` Pekka Enberg [this message]
2012-02-23 16:03 ` Pekka Enberg
2012-02-23 23:17 ` David Rientjes
2012-02-23 23:17 ` David Rientjes
2012-02-24 6:57 ` Pekka Enberg
2012-02-24 6:57 ` Pekka Enberg
2012-02-24 10:03 ` David Rientjes
2012-02-24 10:03 ` David Rientjes
2012-02-24 10:05 ` Pekka Enberg
2012-02-24 10:05 ` Pekka Enberg
2012-02-24 10:38 ` Rafael Aquini
2012-02-24 10:38 ` Rafael Aquini
2012-02-29 3:39 ` Rafael Aquini
2012-02-29 3:39 ` Rafael Aquini
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=1330013036.13624.78.camel@jaguar \
--to=penberg@kernel.org \
--cc=aquini@redhat.com \
--cc=cl@linux-foundation.org \
--cc=josef@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=rdunlap@xenotime.net \
--cc=riel@redhat.com \
--cc=rientjes@google.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 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.