From: Ric Wheeler <ricwheeler@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: [LSF/MM TOPIC] More async operations for file systems - async discard?
Date: Sun, 17 Feb 2019 15:36:10 -0500 [thread overview]
Message-ID: <92ab41f7-35bc-0f56-056f-ed88526b8ea4@gmail.com> (raw)
One proposal for btrfs was that we should look at getting discard out of the
synchronous path in order to minimize the slowdown associated with enabling
discard at mount time. Seems like an obvious win for "hint" like operations like
discard.
I do wonder where we stand now with the cost of the various discard commands -
how painful is it for modern SSD's? Do we have a good sense of how discard
performance scales as the request size increases? Do most devices "no op" a
discard operation when issued against an already discarded region?
Would this be an interesting topic to discuss in a shared block/file system session?
Regards,
Ric
next reply other threads:[~2019-02-17 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 20:36 Ric Wheeler [this message]
2019-02-17 21:09 ` [LSF/MM TOPIC] More async operations for file systems - async discard? Dave Chinner
2019-02-17 23:42 ` Ric Wheeler
2019-02-18 2:22 ` Dave Chinner
2019-02-18 22:30 ` Ric Wheeler
2019-02-20 23:47 ` Keith Busch
2019-02-21 20:08 ` Dave Chinner
2019-02-21 23:55 ` Jeff Mahoney
2019-02-22 3:01 ` Martin K. Petersen
2019-02-22 6:15 ` Roman Mamedov
2019-02-22 14:12 ` Martin K. Petersen
2019-02-22 2:51 ` Martin K. Petersen
2019-02-22 16:45 ` Keith Busch
2019-02-27 11:40 ` Ric Wheeler
2019-02-27 13:24 ` Matthew Wilcox
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=92ab41f7-35bc-0f56-056f-ed88526b8ea4@gmail.com \
--to=ricwheeler@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).