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
> > sk_set_memalloc(sk) on the proper socket, and do some fiddling with the
> > reconnect logic. See nfs-swapfile.patch for examples.
>
> What do you use for testing? I set up ata over ethernet... swapping
> over that should deadlock w/o your patches.
>
> But I'm able to co
examples.
What do you use for testing? I set up ata over ethernet... swapping
over that should deadlock w/o your patches.
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
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
