From: Andi Kleen <ak@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Kimball Murray <kimball.murray@gmail.com>,
linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: [Feature] x86_64 page tracking for Stratus servers
Date: Wed, 6 Sep 2006 09:36:19 +0200 [thread overview]
Message-ID: <200609060936.19268.ak@suse.de> (raw)
In-Reply-To: <44FE6CD6.4040809@yahoo.com.au>
> Silly question, why can't you do all this from stop_machine_run context (or
> your SMI) that doesn't have to worry about other CPUs dirtying memory?
Because that would be too slow for continuous mirroring.
You can't go through 10+GB of virtual memory (or more with shared
memory because the scan has to be virtual) in an interrupt.
The only sane way is to do it continuously.
> [*] Though if it gets included, it would not stop me lamenting the
> proliferation of complexities to support *tiny* obscure userbases. Can
> we wait until your hardware is smart enough to snoop the cc? :)
My guess is that if we had a generic memory mirror subsystem other people would
find uses for it too. e.g. a lot of systems support spare DIMMs these days and mirroring
some memory to it seems like a smart idea. That means normally the hardware
does it, but perhaps some stuff can be done better by doing it in software.
Or it is also a bit similar to the algorithms Xen uses for live migration.
If that was implemented on the kernel level something like this might
be useful too. I think OpenVZ has some kind of migration support, but it's
currently not live.
-andi
next prev parent reply other threads:[~2006-09-06 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 17:34 [Feature] x86_64 page tracking for Stratus servers Kimball Murray
2006-09-05 17:40 ` Arjan van de Ven
2006-09-05 18:38 ` Kimball Murray
2006-09-05 20:48 ` Andi Kleen
2006-09-05 17:56 ` Dave Hansen
2006-09-05 18:50 ` Kimball Murray
2006-09-05 18:16 ` Andi Kleen
2006-09-06 6:38 ` Nick Piggin
2006-09-06 7:36 ` Andi Kleen [this message]
2006-09-06 9:36 ` Nick Piggin
2006-09-06 15:10 ` Kimball Murray
2006-09-06 14:10 ` Kimball Murray
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=200609060936.19268.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@digeo.com \
--cc=kimball.murray@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.