[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1391539464.10160.1.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Tue, 04 Feb 2014 10:44:24 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
netdev@...r.kernel.org, linux-mm@...ck.org,
David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH] fdtable: Avoid triggering OOMs from alloc_fdmem
On Tue, 2014-02-04 at 09:22 -0800, Eric W. Biederman wrote:
> The two code paths below certainly look good canidates for having
> __GFP_NORETRY added to them. The same issues I ran into with
> alloc_fdmem are likely to show up there as well.
Yes, this is what I thought : a write into TCP socket should be more
frequent than the alloc_fdmem() case ;)
But then, maybe your workload was only using UDP ?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists