From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id 0D9107F37 for ; Wed, 8 Jul 2015 20:58:31 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay2.corp.sgi.com (Postfix) with ESMTP id D878D304043 for ; Wed, 8 Jul 2015 18:58:30 -0700 (PDT) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by cuda.sgi.com with ESMTP id QzPAqdNGi8xpQ8ob for ; Wed, 08 Jul 2015 18:58:28 -0700 (PDT) Date: Thu, 9 Jul 2015 11:58:25 +1000 From: Dave Chinner Subject: Re: Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push Message-ID: <20150709015825.GG3902@dastard> References: <20150707233743.GZ7943@dastard> <559D2E52.2070900@unitedstack.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <559D2E52.2070900@unitedstack.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: juncheng bai Cc: linux-kernel , Gavin Guo , xfs@oss.sgi.com On Wed, Jul 08, 2015 at 10:06:10PM +0800, juncheng bai wrote: > Hi, All > > As far as I know, the patch b3f03bac8132207a20286d5602eda64500c19724 > solves one case which big directory size. > > I am not very familiar with xfs, but I think why can't we use vmalloc > when kmalloc fails? Because vmalloc space is greatly limited on 32 bit machines and hence we can't just use vmalloc blindly in these situations. Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs