From: Ray Bryant <raybry@sgi.com>
To: Dave Hansen <dave@sr71.net>
Cc: lhms <lhms-devel@lists.sourceforge.net>,
Marcello Tosatti <marcelo.tosatti@cyclades.com>,
Hirokazu Takahashi <taka@valinux.co.jp>,
linux-mm <linux-mm@kvack.org>
Subject: Re: broken out migration patches
Date: Fri, 07 Jan 2005 18:16:47 -0600 [thread overview]
Message-ID: <41DF266F.6020007@sgi.com> (raw)
In-Reply-To: <1104875977.16305.7.camel@localhost>
Dave,
Looks there is some more work to do here to pull out HOTPLUG
stuff from the migration patches:
==> grep VM_IMMOVABLE page_migration-2.6.10-mm1-mhp-test7.patch
+ if (vma->vm_flags & VM_IMMOVABLE)
+ if (vma->vm_flags & VM_IMMOVABLE)
+#define VM_IMMOVABLE 0x01000000 /* Don't place in hot removable area */
+ _calc_vm_trans(flags, MAP_IMMOVABLE, VM_IMMOVABLE );
+ tmp->vm_flags &= ~(VM_LOCKED|VM_IMMOVABLE);
[raybry@tomahawk.engr.sgi.com:patches/page-migration]
===> grep HOTPLUG page_migration-2.6.10-mm1-mhp-test7.patch
+#ifndef _LINUX_MEMHOTPLUG_H
+#define _LINUX_MEMHOTPLUG_H
+#endif /* _LINUX_MEMHOTPLUG_H */
+#ifdef CONFIG_MEMORY_HOTPLUG
+#ifdef CONFIG_MEMORY_HOTPLUG
+#ifdef CONFIG_MEMORY_HOTPLUG
+#ifdef CONFIG_MEMORY_HOTPLUG
@@ -257,6 +257,8 @@ config HOTPLUG_CPU
The #ifdef's don't hurt anything, really, but it indicates that this
separation isn't clean yet, right?
Should I carry over the VM_IMMOVABLE stuff in the page_migration patch?
--
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>
parent reply other threads:[~2005-01-08 0:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1104875977.16305.7.camel@localhost>]
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=41DF266F.6020007@sgi.com \
--to=raybry@sgi.com \
--cc=dave@sr71.net \
--cc=lhms-devel@lists.sourceforge.net \
--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 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.