On Mon, 2002-03-04 at 11:20, Dieter Nützel wrote:
> Robert I am running 2.4.19-pre2-ac2 + preemption + lock-break.
> It is very snappy due to lock-break I think.
> But lock-break failed on vmscan.c and I didn't apply it by hand this time.
> There was another fail but it was small and easily fixable.
> We need a new lock-break, soon.
-ac2 has rmap and lock-break is not designed for the rmap VM. You can
just ignore the rejects. Further, rmap has some conditional schedules
so you are taken care of.
If rmap finds its way into 2.5, I and others have some ideas about ways
to optimize the algorithms to reduce lock hold time and benefit from
preemption. For example, Daniel Phillips has some ideas wrt
zap_page_range.
> Sadly it is relative hard to put sched-O1-2.4.18-pre8-K3.patch and preemption
> on top of 2.4.19pre2aa1 which I did for several weeks before. The throughput
> with -aa VM maintenance is much better then with -ac.
>
> Latest -aa is 2.4.18-pre8-K3-VM-24-preempt-lock.
Robert Love
-
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/
This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:00:35 EST