Re: [ANNOUNCE] Minneapolis Cluster Summit, July 29-30

[Pavel Machek]

Hi!

> > You missed the point.  The memory deadlock I pointed out occurs in 
> > _normal operation_.  You have to find a way around it, or kernel 
> > cluster services win, plain and simple.
> > 
> 
> The bottom line is that we just don't know if any such deadlock occurs,
> under normal operations.  The remaining objections to in-kernel cluster

I did some work on swapping-over-nbd, which has similar issues,
and yes, the deadlocks were seen under heavy load.

*Designing* something with "lets hope it does not deadlock",
while deadlock clearly can be triggered, looks like bad idea.
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/