From: Avi Kivity <avi@redhat.com>
To: Kallol Biswas <nucleodyne@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: looking for ideas on VM related research projects
Date: Tue, 09 Jun 2009 11:25:11 +0300 [thread overview]
Message-ID: <4A2E1C67.4040301@redhat.com> (raw)
In-Reply-To: <438397970906090114m7ebc6e6fub0c6085f462d2e1a@mail.gmail.com>
Kallol Biswas wrote:
> Hi,
> I am from IO and driver background, and not up to date with
> current VM developments in linux.
>
> Are you talking about NUMA architecture?
Yes.
> Could you clarify or point me
> to document that describes the problem with VMA/task affinity?
Linux will try to allocate memory on the same node that the allocating
thread ran on on the time the page was faulted in. However, for long
running processes, the thread will eventually migrate to some other cpu
with only 1/N chance of actually running on the same node (N being the
number of nodes).
If we can specify that a thread is related to some vma, the scheduler
can try to keep that thread running on the vma's node, or else it can
migrate the vma to a node with available cpu power.
> Where do affinity issues arise?
>
Large, long-running processes. My specific interest is virtualization
with kvm, but I believe HPC and databases can make use of this as well.
HPC currently solves the problem by statically allocating memory and cpu
resources.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-09 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 5:49 looking for ideas on VM related research projects Kallol Biswas
2009-06-08 6:14 ` Avi Kivity
2009-06-09 8:14 ` Kallol Biswas
2009-06-09 8:25 ` Avi Kivity [this message]
2009-06-08 21:52 ` Wes Felter
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=4A2E1C67.4040301@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nucleodyne@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox