From: Matthew Wilcox <willy@infradead.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
ceph-devel@vger.kernel.org, idryomov@gmail.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ceph: Uninline the data on a file opened for writing
Date: Fri, 17 Dec 2021 17:29:59 +0000 [thread overview]
Message-ID: <YbzJFytPgSbuh1bx@casper.infradead.org> (raw)
In-Reply-To: <e2fcdecb9288dc112d0051e917da5bb48bf72388.camel@kernel.org>
On Fri, Dec 17, 2021 at 12:18:04PM -0500, Jeff Layton wrote:
> This feature is being deprecated in ceph altogether, so more
> aggressively uninlining of files is fine. The kernel cephfs client never
> supported writes to it anyway so this feature was really only used by a
> few brave souls.
>
> We're hoping to have it formally removed by the time the Ceph Quincy
> release ships (~April-May timeframe). Unfortunately, we need to keep
> support for it around for a bit longer since some still-supported ceph
> releases don't have this deprecated.
OK, I shan't bother pointing out the awful bugs and races in the current
uninlining code then ...
prev parent reply other threads:[~2021-12-17 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:29 [PATCH v2 1/2] ceph: Uninline the data on a file opened for writing David Howells
2021-12-17 15:29 ` [PATCH v2 2/2] ceph: Remove some other inline-setting bits David Howells
2021-12-17 16:07 ` Jeff Layton
2021-12-17 16:05 ` [PATCH v2 1/2] ceph: Uninline the data on a file opened for writing Jeff Layton
2021-12-17 16:20 ` Matthew Wilcox
2021-12-17 17:18 ` Jeff Layton
2021-12-17 17:29 ` Matthew Wilcox [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=YbzJFytPgSbuh1bx@casper.infradead.org \
--to=willy@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@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).