From: Dave Chinner <david@fromorbit.com>
To: juncheng bai <baijuncheng@unitedstack.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Gavin Guo <gavin.guo@canonical.com>,
xfs@oss.sgi.com
Subject: Re: Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push
Date: Thu, 9 Jul 2015 11:58:25 +1000 [thread overview]
Message-ID: <20150709015825.GG3902@dastard> (raw)
In-Reply-To: <559D2E52.2070900@unitedstack.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
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: juncheng bai <baijuncheng@unitedstack.com>
Cc: Gavin Guo <gavin.guo@canonical.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push
Date: Thu, 9 Jul 2015 11:58:25 +1000 [thread overview]
Message-ID: <20150709015825.GG3902@dastard> (raw)
In-Reply-To: <559D2E52.2070900@unitedstack.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
next prev parent reply other threads:[~2015-07-09 1:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:29 Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push Gavin Guo
2015-07-07 9:29 ` Gavin Guo
2015-07-07 23:37 ` Dave Chinner
2015-07-07 23:37 ` Dave Chinner
2015-07-08 12:34 ` Gavin Guo
2015-07-08 12:34 ` Gavin Guo
2015-07-08 14:06 ` juncheng bai
2015-07-08 14:06 ` juncheng bai
2015-07-09 1:58 ` Dave Chinner [this message]
2015-07-09 1:58 ` Dave Chinner
2015-08-28 12:54 ` Gavin Guo
2015-08-28 12:54 ` Gavin Guo
2015-08-29 22:31 ` Dave Chinner
2015-08-29 22:31 ` Dave Chinner
2015-08-31 7:33 ` Gavin Guo
2015-08-31 7:33 ` Gavin Guo
2015-12-07 16:46 ` Gavin Guo
2015-12-07 16:46 ` Gavin Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150709015825.GG3902@dastard \
--to=david@fromorbit.com \
--cc=baijuncheng@unitedstack.com \
--cc=gavin.guo@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.