Re: [PATCH] Deadlock during heavy write activity to userspace NFS

[Nick Piggin]

Ulrich Weigand wrote:

> Nick Piggin wrote:
>
>
> > Avi Kivity wrote:
> >
> > > The kernel NFS client (which kswapd depends on) has the same issue. Has 
> > > anyone ever observed kswapd deadlock due to imcoming or outgoing NFS 
> > > packets being discarded due to oom?
> > Yes this has been observed.
> >
> > alloc_skb on the client needs to somehow know that traffic coming
> > from the server is "MEMALLOC" and allowed to use memory reserves.
>
> What would be an appropriate way to solve this problem? A special
> socket option?

What I think was happening is dirty NFS pages being written out in response
to low memory. The acks coming back from the server weren't being received
because memory couldn't be allocated for them.

Ideally you would allow the NFS path to allocate enough memory that it can
guarantee forward progress - like how the block layer uses mempools for
struct requests, for example.

-
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/