public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Lazy NUMA sorting?
Date: Thu, 15 Apr 2004 17:12:11 -0400	[thread overview]
Message-ID: <407EFAAB.7060307@techsource.com> (raw)

So, I understand that the 2.6 SMP balancer redistributes workload on a 
periodic basis.  Once every second or something, it migrates processes.

A NUMA system would have to do something similar, where if there is a 
page which is referenced by only one process, and the page is located on 
the "wrong" node, it could be migrated.  This could be done gradually by 
a periodic background process.  Is this already how it works?

Also, if a page is being referenced by multiple nodes, the same 
background process could make mirror copies.  (Age of page would be an 
important consideration here so moves don't happen for short-lived pages.)


             reply	other threads:[~2004-04-15 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 21:12 Timothy Miller [this message]
2004-04-15 22:07 ` Lazy NUMA sorting? Martin J. Bligh

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=407EFAAB.7060307@techsource.com \
    --to=miller@techsource.com \
    --cc=linux-kernel@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