Hi!
> > But I'm able to compile kernel (-j 10) on 128MB machine, and I tried
> > cat /dev/zero | grep foo to exhaust memory... and could not reproduce
> > the deadlock. Should I pingflood? Tweak down ammount of atomic memory
> > avaialable to make deadlocks easier to reproduce?
>
> I usually test
On Thu, 2007-08-09 at 12:11 +0200, Pavel Machek wrote:
> Hi!
>
> > I've been working on this for quite some time. And should post again
> > soon. Please see the patches:
> >
> > http://programming.kicks-ass.net/kernel-patches/vm_deadlock/current/
> >
> > For now it requires one uses SLUB, I ho
Hi!
> I've been working on this for quite some time. And should post again
> soon. Please see the patches:
>
> http://programming.kicks-ass.net/kernel-patches/vm_deadlock/current/
>
> For now it requires one uses SLUB, I hope that SLAB will go away (will
> save me the trouble of adding support
I've been working on this for quite some time. And should post again
soon. Please see the patches:
http://programming.kicks-ass.net/kernel-patches/vm_deadlock/current/
For now it requires one uses SLUB, I hope that SLAB will go away (will
save me the trouble of adding support) and I guess I oug
Hi!
> ...
> > Is the protocol documented somewhere? aoe.txt only points at
> > HOWTO... aha, protocol is linked from wikipedia.
> > http://www.coraid.com/documents/AoEr10.txt ... perhaps that should be
> > linked from aoe.txt, too?
>
> Perhaps. Most people reading the aoe.txt file won't need to