From: Ray Bryant <raybry@sgi.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Hirokazu Takahashi <taka@valinux.co.jp>
Cc: linux-mm <linux-mm@kvack.org>
Subject: manual page migration, revisited...
Date: Fri, 05 Nov 2004 16:50:53 -0600 [thread overview]
Message-ID: <418C03CD.2080501@sgi.com> (raw)
Marcelo and Takahashi-san (and anyone else who would like to comment),
This is a little off topic, but this is as good of thread as any to start this
discussion on. Feel free to peel this off as a separate discussion thread
asap if you like.
We have a requirement (for a potential customer) to do the following kind of
thing:
(1) Suspend and swap out a running process so that the node where the process
is running can be reassigned to a higher priority job.
(2) Resume and swap back in those suspended jobs, restoring the original
memory layout on the original nodes, or
(3) Resume and swap back in those suspended jobs on a new set of nodes, with
as similar topological layout as possible. (It's also possible we may
want to just move the jobs directly from one set of nodes to another
without swapping them out first.
This is all in the context of a batch scheduler being used to run jobs on
a large paralell machine.
As I understand it, there are various patches floating around (including the
migration code that you are working on, the memory hotplug removal code, etc)
that do parts of this, but I've had a little trouble piecing together the
status of those various patches and where to get them. (e. g. where do I get
the latest migration cache code?).
There was also a thread in early April 2004 on this list about manual page
migration, I think, but I don't know where that went, if anywhere (that would
satisfy requirement 3.)
So the question I am asking, I guess, is where would you suggest we start on
an implementation for something like the above? Which existing bits and
peices can I pick up, if anything, from your migration cache work and or the
memory hotplug work, do you think? Or, which patches should I be looking at
for ideas?
I'm not asking you to >>do<< this work, of course, I'm just trying to get a
start on the above and not unecessarily duplicate anyone's previous work in
this area. Any pointers or advice would be greatly appeciated.
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
--
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>
next reply other threads:[~2004-11-05 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 22:50 Ray Bryant [this message]
2004-11-05 23:02 ` Nigel Cunningham
2004-11-06 17:48 ` Marcelo Tosatti
2004-11-07 2:58 ` Nigel Cunningham
2004-11-07 5:08 ` Ray Bryant
2004-11-07 11:19 ` Hirokazu Takahashi
2004-11-07 4:57 ` Ray Bryant
2004-11-07 21:11 ` Nigel Cunningham
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=418C03CD.2080501@sgi.com \
--to=raybry@sgi.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=taka@valinux.co.jp \
/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