On Wed, 2012-06-27 at 15:28 -0400, Jeff Layton wrote:
> On Wed, 27 Jun 2012 18:43:56 +0000
> "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> wrote:
> If there really is no alternative to freeing the socket, then the only
> real fix I can see is to set PF_MEMALLOC when we go to create it and
> then reset it afterward. That's a pretty ugly fix though...
I can think of 2 possible alternatives:
1. Use the PF_FSTRANS flag to tell nfs_release_page that this is a
direct reclaim from rpciod.
2. Add a 'congested' flag to the rpc client that could tell reclaim
type operations to give up if a socket allocation is in
progress.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
