On Mon, 2002-01-14 at 17:40, Heinz Diehl wrote: > > After that you should apply preempt+locl-break or LL to both. > > The same here, lock-break does not apply to 2.4.18-pre3+H7 without > some failed hunks.... Just a note, if lock-break fails in chunks it is probably OK to just ignore them. Each lock-break is independent so, while it is less lock breaking, it is nearly the same and certainly works fine. Wouldn't give the same advice for rmap, however. Best to make sure your VM applies cleanly :) Robert Love - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: slowdown with new scheduler.Dieter =?iso-8859-15?q?N=FCtzel?= <Dieter.Nuetzel _at_ hamburg.de>
- Re: slowdown with new scheduler.Heinz Diehl <hd _at_ cavy.de>
- Prev by Date: Re: Penelope builds a kernel
- Next by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Previous by thread: Re: slowdown with new scheduler.
- Next by thread: IDE code
- Indexes:[Main][Thread]