Messages in this thread | | | Date | Thu, 10 Sep 2009 12:11:37 +0200 | From | Jens Axboe <> | Subject | Re: BFS vs. mainline scheduler benchmarks and measurements |
| |
On Thu, Sep 10 2009, Ingo Molnar wrote: > > * Jens Axboe <jens.axboe@oracle.com> wrote: > > > On Thu, Sep 10 2009, Ingo Molnar wrote: > > > > > > * Ingo Molnar <mingo@elte.hu> wrote: > > > > > > > > However, the interactivity problems still remain. Does that > > > > > mean it's not a latency issue? > > > > > > > > It means that Jens's test-app, which demonstrated and helped us > > > > fix the issue for him does not help us fix it for you just yet. > > > > > > Lemme qualify that by saying that Jens's issues are improved not > > > fixed [he has not re-run with latest latt.c yet] but not all things > > > are fully fixed yet. For example the xmodmap thing sounds > > > interesting - could that be a child-runs-first effect? > > > > I thought so too, so when -tip failed to boot I pulled the patches > > from Mike into 2.6.31. It doesn't change anything for xmodmap, > > though. > > Note, you can access just the pristine scheduler patches by checking > out and testing tip:sched/core - no need to pull them out and apply. > > Your crash looks like clocksource related - that's in a separate > topic which you can thus isolate if you use sched/core.
I'm building sched/core now and will run the xmodmap test there.
-- Jens Axboe
| |