On Fri, 2008-06-20 at 00:32 +0900, kamezawa.hiroyu@xxxxxxxxxxxxxx wrote: > ----- Original Message ----- > >Subject: Re: [Experimental][PATCH] putback_lru_page rework > >From: Lee Schermerhorn <Lee.Schermerhorn@xxxxxx> > > >On Thu, 2008-06-19 at 09:22 +0900, KAMEZAWA Hiroyuki wrote: > >> On Wed, 18 Jun 2008 14:21:06 -0400 > >> Lee Schermerhorn <Lee.Schermerhorn@xxxxxx> wrote: > >> > >> > On Wed, 2008-06-18 at 18:40 +0900, KAMEZAWA Hiroyuki wrote: > >> > > Lee-san, how about this ? > >> > > Tested on x86-64 and tried Nisimura-san's test at el. works good now. > >> > > >> > I have been testing with my work load on both ia64 and x86_64 and it > >> > seems to be working well. I'll let them run for a day or so. > >> > > >> thank you. > >> <snip> > > > >Update: > > > >On x86_64 [32GB, 4xdual-core Opteron], my work load has run for ~20:40 > >hours. Still running. > > > >On ia64 [32G, 16cpu, 4 node], the system started going into softlockup > >after ~7 hours. Stack trace [below] indicates zone-lru lock in > >__page_cache_release() called from put_page(). Either heavy contention > >or failure to unlock. Note that previous run, with patches to > >putback_lru_page() and unmap_and_move(), the same load ran for ~18 hours > >before I shut it down to try these patches. > > > Thanks, then there are more troubles should be shooted down. > > > >I'm going to try again with the collected patches posted by Kosaki-san > >[for which, Thanks!]. If it occurs again, I'll deconfig the unevictable > >lru feature and see if I can reproduce it there. It may be unrelated to > >the unevictable lru patches. > > > I hope so...Hmm..I'll dig tomorrow. Another update--with the collected patches: Again, the x86_64 ran for > 22 hours w/o error before I shut it down. And, again, the ia64 went into soft lockup--same stack traces. This time after > 17 hours of running. It is possible that a BUG started this, but it has long scrolled out of my terminal buffer by the time I see the system. I'm now trying the ia64 platform with 26-rc5-mm3 + collected patches with UNEVICTABLE_LRU de-configured. I'll start that up today and let it run over the weekend [with panic_on_oops set] if it hasn't hit the problem before I leave. Regards, Lee -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
