linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neal Gompa <ngompa13@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	Chris Murphy <lists@colorremedies.com>
Subject: Using async discard by default with SSDs?
Date: Thu, 21 Jul 2022 14:43:16 -0400	[thread overview]
Message-ID: <CAEg-Je_b1YtdsCR0zS5XZ_SbvJgN70ezwvRwLiCZgDGLbeMB=w@mail.gmail.com> (raw)

Hey all,

I was talking with Chris Mason today at a Fedora Hatch event about
async discards (as we were thinking about doing this in Fedora some
time ago[1]), and he seemed to consider it reasonable to make it so
Btrfs uses async discards by default when being formatted on SSDs.

He and I couldn't think of a reason why not to, other than the
potential lack of "discard=none" option to turn off discards if the
user wanted it to. Do we already have this option? Are there any other
reasons not to do this? Or is this something we should have changed in
Btrfs so everyone gets async discards by default going forward?

Thanks in advance and best regards,
Neal

[1]: https://pagure.io/fedora-btrfs/project/issue/6

--
真実はいつも一つ！/ Always, there's only one truth!

             reply	other threads:[~2022-07-21 18:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 18:43 Neal Gompa [this message]
2022-07-21 19:21 ` Using async discard by default with SSDs? Roman Mamedov
2022-07-25 19:08 ` David Sterba
2022-07-26 20:00   ` Chris Murphy
2022-07-26 21:36     ` David Sterba
2022-07-26 22:10       ` Chris Murphy
2022-07-27 14:50         ` Chris Murphy
2022-07-27 14:56           ` David Sterba
2022-07-27 15:14             ` Chris Murphy
2022-07-27 17:47               ` David Sterba
2022-07-28 12:27                 ` Chris Murphy
2022-07-27 15:26             ` Neal Gompa
2022-08-05 15:14             ` David Sterba

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='CAEg-Je_b1YtdsCR0zS5XZ_SbvJgN70ezwvRwLiCZgDGLbeMB=w@mail.gmail.com' \
    --to=ngompa13@gmail.com \
    --cc=clm@fb.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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).