From: Emmanuel Florac <eflorac@intellique.com>
To: Brian Foster <bfoster@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
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: Fri, 21 Feb 2020 13:52:59 +0100 [thread overview]
Message-ID: <20200221135259.0dc80197@harpe.intellique.com> (raw)
In-Reply-To: <20200221121509.GA2053@bfoster>
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
Le Fri, 21 Feb 2020 07:15:09 -0500
Brian Foster <bfoster@redhat.com> écrivait:
> > There are almost always downstream modifications in private cloud
> > storage kernels, even if it is just bug fixes. They aren't shipping
> > the code to anyone, so they don't have to publish those changes.
> > However, the presence of downstream changes doesn't mean the
> > upstreram functionality should be considered unused and can be
> > removed....
> >
>
> Well that's not what I said. ;P I'm pointing out that as of right now
> this is a downstream only use case. I know there was upstream
> communication and patches posted, etc., but that was a while ago and
> it wasn't clear to me if there was still intent to get things merged
> upstream. If not, then the only real outcome here for anybody outside
> of FB is bitrot.
Maybe, maybe not. Storage tiering is a pretty hot subject, simply
shedding some light on this capability may give it more use. I didn't
know of any actual use case for RT in XFS since IRIX times, but if
there's a way to use it for tiering, this is indeed a very promising
area of development for me (and no doubt many others).
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
prev parent reply other threads:[~2020-02-21 13:01 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
2020-02-20 22:06 ` Dave Chinner
2020-02-21 12:15 ` Brian Foster
2020-02-21 12:52 ` Emmanuel Florac [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=20200221135259.0dc80197@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=ailiopoulos@suse.de \
--cc=bfoster@redhat.com \
--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).