From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Richard Wareing <rwareing@fb.com>,
linux-xfs@vger.kernel.org,
Anthony Iliopoulos <ailiopoulos@suse.de>
Subject: Re: Modern uses of CONFIG_XFS_RT
Date: Thu, 20 Feb 2020 09:25:20 -0500 [thread overview]
Message-ID: <20200220142520.GF48977@bfoster> (raw)
In-Reply-To: <20200220034106.GO10776@dread.disaster.area>
On Thu, Feb 20, 2020 at 02:41:06PM +1100, Dave Chinner wrote:
> On Wed, Feb 19, 2020 at 01:57:15PM +0000, Luis Chamberlain wrote:
> > I hear some folks still use CONFIG_XFS_RT, I was curious what was the
> > actual modern typical use case for it. I thought this was somewhat
> > realted to DAX use but upon a quick code inspection I see direct
> > realtionship.
>
> Facebook use it in production systems to separate large file data
> from metadata and small files. i.e. they use a small SSD based
> partition for the filesytem metadata and a spinning disk for
> the large scale data storage. Essentially simple teired storage.
>
Didn't this involve custom functionality? I thought they had posted
something at one point that wasn't seen through to merge, but I could be
misremembering (or maybe that was something else RT related). It doesn't
matter that much as there are probably other users out there, but I'm
not sure this serves as a great example use case if it did require
downstream customizations that aren't going to be generalized/supported
for the community.. Richard..?
Brian
> It's also commonly still used in multi-stream DVRs (think
> multi-camera security systems), and other similar sequential access
> data applications...
>
> That's just a couple off the top of my head...
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
next prev parent reply other threads:[~2020-02-20 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 13:57 Modern uses of CONFIG_XFS_RT Luis Chamberlain
2020-02-19 14:32 ` Carlos Maiolino
2020-02-19 14:38 ` Luis Chamberlain
2020-02-19 17:09 ` Darrick J. Wong
2020-02-19 17:55 ` Luis Chamberlain
2020-02-19 22:01 ` Darrick J. Wong
2020-02-20 0:17 ` Luis Chamberlain
2020-02-20 2:03 ` Darrick J. Wong
2020-02-20 2:12 ` Eric Sandeen
2020-02-20 2:15 ` Darrick J. Wong
2020-02-20 3:41 ` Dave Chinner
2020-02-20 14:25 ` Brian Foster [this message]
2020-02-20 22:06 ` Dave Chinner
2020-02-21 12:15 ` Brian Foster
2020-02-21 12:52 ` Emmanuel Florac
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=20200220142520.GF48977@bfoster \
--to=bfoster@redhat.com \
--cc=ailiopoulos@suse.de \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).