On Wed, 2009-06-17 at 10:22 +0900, KAMEZAWA Hiroyuki wrote: > On Tue, 16 Jun 2009 10:59:55 -0400 > Lee Schermerhorn <Lee.Schermerhorn@xxxxxx> wrote: > > > On Tue, 2009-06-16 at 15:58 +0200, Stefan Lankes wrote: > > > > > > > > I would like to get these patches working with latest mmotm to test on > > > > some newer hardware where I think they will help more. And I would > > > > welcome your support. However, I think we'll need to get Balbir and > > > > Kamezawa-san involved to sort out the interaction with memory control > > > > group. > > > > > > > > I can send you the more recent rebase that I've done. This is getting > > > > pretty old now: 2.6.28-rc4-mmotm-081110-081117. I'll try to rebase to > > > > the most recent mmotm [that boots on my platforms], at least so that we > > > > can build and boot with migrate-on-fault disabled, within the next > > > > couple of weeks. > > > > > > > > > > Sounds good! Send me your last version and I will try to reconstruct your > > > problems. Afterwards, we could try to solve these problems. > > > > > > > Stefan: > > > > I've placed the last rebased version in : > > > > http://free.linux.hp.com/~lts/Patches/PageMigration/2.6.28-rc4-mmotm-081110/ > > > > As I recall, this version DOES bug out because of reference count > > problems due to interaction with the memory controller. > > > please report in precise if memcg has bug. > An example of test is welcome. Not an memcg bug. Just an implementation choice [2 phase migration handling: start/end calls] that is problematic for "lazy" page migration--i.e., "migration-on-touch" in the fault path. I'd be interested in your opinion on the feasibility of transferring the "charge" against the page--including the "try charge" from do_swap_page()--in migrate_page_copy() along with other page state. I'll try to rebase my lazy migration series to recent mmotm [as time permits] in the "near future" and gather more info on the problem I was having. Regards, Lee -- To unsubscribe from this list: send the line "unsubscribe linux-numa" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
