From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, linux-mm@kvack.org
Subject: Re: Profiling: Require buffer allocation on the correct node
Date: Thu, 10 Aug 2006 05:21:19 +0200 [thread overview]
Message-ID: <200608100521.19783.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0608091914470.5464@schroedinger.engr.sgi.com>
On Thursday 10 August 2006 04:18, Christoph Lameter wrote:
> Profiling really suffers with off node buffers. Fail if no memory is available
> on the nodes. The profiling code can deal with these failures should
> they occur.
At least for Opterons and other small NUMAs I have my doubts this is a good strategy.
However it probably shouldn't happen very often, but if it happened it would be
the wrong thing.
In general shouldn't there be a printk at least? Doing such things silently is a bit
nasty.
-Andi
--
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:[~2006-08-10 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 2:18 Profiling: Require buffer allocation on the correct node Christoph Lameter
2006-08-10 3:21 ` Andi Kleen [this message]
2006-08-10 4:53 ` Christoph Lameter
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=200608100521.19783.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--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 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.