On Mon, 2005-02-14 at 07:52 -0600, Robin Holt wrote: > The node mask is a list of allowed. This is intended to be as near > to a one-to-one migration path as possible.
If that's the case, it would make the kernel internals a bit simpler to only take a "from" and "to" node, instead of those maps. You'll end up making multiple syscalls, but that shouldn't be a problem. > > There also probably needs to be a bit more coordination between the > > other NUMA API and this one. I noticed that, for now, the migration > > loop only makes a limited number of passes. It appears that either you > > don't require that, once the syscall returns, that *all* pages have been > > migrated (there could have been allocations done behind the loop) or you > > have some way of keeping the process from doing any more allocations. > > It is intended that the process would be stopped during the migration > to simplify considerations such as overlapping destination node lists. Requiring that the process is stopped will somewhat limit the use of this API outside of the HPC space where so much control can be had over the processes. I have the feeling that very few other kinds of applications will be willing to be stopped for the time that it takes for a set of migrations to occur. But, if stopping the process is going to be a requirement, having more syscalls that take less time each should be desirable. -- Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
