From: Christoph Hellwig <hch@infradead.org>
To: Richard Wareing <rwareing@fb.com>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com, darrick.wong@oracle.com
Subject: Re: [PATCH v2 3/3] fs/xfs: Add rtfallocmin mount option
Date: Sun, 3 Sep 2017 01:50:13 -0700 [thread overview]
Message-ID: <20170903085013.GE32385@infradead.org> (raw)
In-Reply-To: <20170902224145.1291030-4-rwareing@fb.com>
On Sat, Sep 02, 2017 at 03:41:45PM -0700, Richard Wareing wrote:
> - Gates real-time block device fallocation's to rtfallocmin bytes
> - Use case: Allows developers to send files to the SSD with ease simply
> by fallocating them, if they are below rtfallocmin XFS will allocate the
> blocks from the non-RT device (e.g. an SSD)
> - Useful to automagically store small files on the SSD vs. RT device
> (HDD) for tiered XFS setups without having to rely on XFS specific
> ioctl calls. Userland tools such as rsync can also use fallocation
> behavior to migrate files between SSD and RT (HDD) device without
> modifiction (e.g. w/ --preallocate flag).
I'd be much happier if this was done inside the allocator, and in
affect for any initial allocation, not just fallocate, as that keeps
the layering and logic much cleaner.
next prev parent reply other threads:[~2017-09-03 8:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 22:41 [PATCH v2 0/3] XFS real-time device tweaks Richard Wareing
2017-09-02 22:41 ` [PATCH v2 1/3] fs/xfs: Add rtdisable option Richard Wareing
2017-09-02 22:41 ` [PATCH v2 2/3] fs/xfs: Add real-time device support to statfs Richard Wareing
2017-09-03 8:49 ` Christoph Hellwig
2017-09-02 22:41 ` [PATCH v2 3/3] fs/xfs: Add rtfallocmin mount option Richard Wareing
2017-09-03 8:50 ` Christoph Hellwig [this message]
2017-09-03 22:04 ` Richard Wareing
2017-09-03 8:56 ` [PATCH v2 0/3] XFS real-time device tweaks Christoph Hellwig
2017-09-03 22:02 ` Richard Wareing
2017-09-06 3:44 ` Dave Chinner
2017-09-06 6:54 ` Richard Wareing
2017-09-06 11:19 ` Dave Chinner
2017-09-06 11:43 ` Brian Foster
2017-09-06 12:12 ` Dave Chinner
2017-09-06 12:49 ` Brian Foster
2017-09-06 23:29 ` Dave Chinner
2017-09-07 11:58 ` Brian Foster
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=20170903085013.GE32385@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=rwareing@fb.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