From: Dave Chinner <david@fromorbit.com>
To: Cyril PEPONNET <cyril.peponnet@nuagenetworks.net>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc on glusterfs setup
Date: Thu, 8 Dec 2016 06:44:02 +1100 [thread overview]
Message-ID: <20161207194402.GJ4326@dastard> (raw)
In-Reply-To: <8176484246282250577@unknownmsgid>
On Wed, Dec 07, 2016 at 07:16:55AM -0800, Cyril PEPONNET wrote:
> Our snapshots are deleted / recreated quite often. If I apply the extent
> size hint to the root folder of an existing tree, does it will still apply
> for new created files ?
Only for new files/directories created in the root directory. THe
hint is not retro-actively applied. You'd need to walk the tree
setting the hint on all directories to get it to apply to all new
files created.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-12-07 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 19:08 XFS: possible memory allocation deadlock in kmem_alloc on glusterfs setup Cyril Peponnet
2016-12-04 21:49 ` Dave Chinner
2016-12-04 22:07 ` Cyril Peponnet
2016-12-04 22:46 ` Dave Chinner
2016-12-04 23:24 ` Cyril Peponnet
2016-12-04 23:50 ` Dave Chinner
2016-12-05 1:14 ` Cyril Peponnet
2016-12-05 1:22 ` Dave Chinner
2016-12-05 1:48 ` Cyril Peponnet
[not found] ` <C07DD929-5600-4934-A6B0-C0A7D83D7247@nuagenetworks.net>
2016-12-05 7:46 ` Dave Chinner
2016-12-05 15:51 ` Cyril Peponnet
2016-12-05 21:45 ` Dave Chinner
2016-12-06 17:54 ` Cyril Peponnet
2016-12-07 6:16 ` Dave Chinner
[not found] ` <473936408.4772.1481091425441@itfw6.prod.google.com>
[not found] ` <8176484246282250577@unknownmsgid>
2016-12-07 19:44 ` Dave Chinner [this message]
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=20161207194402.GJ4326@dastard \
--to=david@fromorbit.com \
--cc=cyril.peponnet@nuagenetworks.net \
--cc=linux-xfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).