From: David Rientjes <rientjes@google.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
dave@linux.vnet.ibm.com, mgorman@suse.de, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: + mm-show_mem-suppress-page-counts-in-non-blockable-contexts.patch added to -mm tree
Date: Fri, 1 Mar 2013 02:15:04 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1303010213140.23298@chino.kir.corp.google.com> (raw)
In-Reply-To: <20130301095716.GA21443@dhcp22.suse.cz>
On Fri, 1 Mar 2013, Michal Hocko wrote:
> I have already asked about it in the original thread but didn't get any
> answer. How can we get a soft lockup when all implementations of show_mem
> call touch_nmi_watchdog?
>
Feel free to do s/soft lockups/irqs being disabled for an extremely long
time/.
> I do agree with the change but the above justification seems misleading.
> Can we just remove the information because it is costly and doesn't give
> us anything relevant to debug allocation failures?
>
I believe I have already said yes, that all pertinent information is
already there and I do not believe this additional information
continuously spewed to the kernel log is helpful in debugging VM issues or
understanding why the oom condition exists.
--
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-03-01 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130228231025.9F11A5A410E@corp2gmr1-2.hot.corp.google.com>
2013-03-01 9:57 ` Michal Hocko
2013-03-01 10:15 ` David Rientjes [this message]
2013-03-01 10:23 ` Michal Hocko
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=alpine.DEB.2.02.1303010213140.23298@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.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