From: "Kani, Toshi" <toshi.kani@hpe.com>
To: "david@fromorbit.com" <david@fromorbit.com>
Cc: "ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: DAX 2MB mappings for XFS
Date: Fri, 12 Jan 2018 21:38:22 +0000 [thread overview]
Message-ID: <1515795857.16384.34.camel@hpe.com> (raw)
In-Reply-To: <20180112211915.GF27323@dastard>
On Sat, 2018-01-13 at 08:19 +1100, Dave Chinner wrote:
:
> IOWs, what you are seeing is trying to do a very large allocation on
> a very small (8GB) XFS filesystem. It's rare someone asks to
> allocate >25% of the filesystem space in one allocation, so it's not
> surprising it triggers ENOSPC-like algorithms because it doesn't fit
> into a single AG....
>
> We can probably look to optimise this, but I'm not sure if we can
> easily differentiate this case (i.e. allocation request larger than
> continguous free space) from the same situation near ENOSPC when we
> really do have to trim to fit...
>
> Remember: stripe unit allocation alignment is a hint in XFS that we
> can and do ignore when necessary - it's not a binding rule.
Thanks for the clarification! Can XFS allocate smaller extents so that
each extent will fit to an AG? ext4 creates multiple smaller extents
for the same request.
-Toshi
next prev parent reply other threads:[~2018-01-12 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 19:40 DAX 2MB mappings for XFS Kani, Toshi
2018-01-12 21:19 ` Dave Chinner
2018-01-12 21:38 ` Kani, Toshi [this message]
2018-01-12 22:27 ` Dave Chinner
2018-01-12 23:15 ` Kani, Toshi
2018-01-12 23:52 ` Darrick J. Wong
2018-01-13 0:05 ` Kani, Toshi
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=1515795857.16384.34.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.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 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).