Messages in this thread | | | Date | Tue, 15 Feb 2005 03:14:48 -0600 | From | Ray Bryant <> | Subject | Re: [RFC 2.6.11-rc2-mm2 0/7] mm: manual page migration -- overview |
| |
Paul Jackson wrote: > Ray wrote: > >>[Thus the disclaimer in >>the overview note that we have figured all the interaction with >>memory policy stuff yet.] > > > Does the same disclaimer apply to cpusets? > > Unless it causes some undo pain, I would think that page migration > should _not_ violate a tasks cpuset. I guess this means that a typical > batch manager would move a task to its new cpuset on the new nodes, or > move the cpuset containing some tasks to their new nodes, before asking > the page migrator to drag along the currently allocated pages from the > old location. > No, I think we understand the interaction between manual page migration and cpusets. We've tried to keep the discussion here disjoint from cpusets for tactical reasons -- we didn't want to tie acceptance of the manual page migration code to acceptance of cpusets.
The exact ordering of when a task is moved to a new cpuset and when the migration occurs doesn't matter, AFAIK, if we accept the notion that a migrated task is in suspended state until after everything associated with it (including the new cpuset definition) is done.
-- ----------------------------------------------- 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |