linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Christoph Lameter <christoph@lameter.com>
Cc: Robin Holt <holt@sgi.com>, linux-mm@kvack.org
Subject: Re: Is there a way to do an architecture specific shake of memory?
Date: Wed, 9 Mar 2005 06:14:35 -0600	[thread overview]
Message-ID: <20050309121435.GA29630@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503081833430.10095@server.graphe.net>

On Tue, Mar 08, 2005 at 06:35:07PM -0800, Christoph Lameter wrote:
> On Tue, 8 Mar 2005, Robin Holt wrote:
> 
> > Any suggestions are welcome.
> 
> Check when you free items how long the list of free items is and if its
> too long free some of them.

That is done as well as a check from cpu_idle.  The amount of free is
being changed from a boot-time very large number computed from total
memory to a per-node percentage of free memory.  A concern was raised
for the eventuality of a process constantly running on a cpu so the idle
calls never happen, a memory hog application begins to consume memory on
the node, and nothing ever shakes the memory free from the quicklists.
This led to the suggestion of a timer based shaker.  I would rather put
it into the blocked allocation path than have it timer based and hope
we pick the correct resolution of timer.  The problem is the quicklists
are per-cpu so we need to try flushing the quicklists for the cpus on
the affected node.

Thanks,
Robin Holt
--
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:"aart@kvack.org"> aart@kvack.org </a>

      reply	other threads:[~2005-03-09 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 21:15 Robin Holt
2005-03-09  2:35 ` Christoph Lameter
2005-03-09 12:14   ` Robin Holt [this message]

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=20050309121435.GA29630@lnx-holt.americas.sgi.com \
    --to=holt@sgi.com \
    --cc=christoph@lameter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox