From: Christoph Hellwig <hch@lst.de>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fat: make discard a mount option
Date: Wed, 18 Nov 2009 19:53:58 +0100 [thread overview]
Message-ID: <20091118185358.GA29399@lst.de> (raw)
In-Reply-To: <87d43f4r1v.fsf@devron.myhome.or.jp>
On Thu, Nov 19, 2009 at 03:38:04AM +0900, OGAWA Hirofumi wrote:
> Christoph Hellwig <hch@lst.de> writes:
>
> > Currently shipping discard capable SSDs and arrays have rather sub-optimal
> > implementations of the command and can the use of it can cause massive
> > slowdowns. Make issueing these commands option as it's already in btrfs
> > and gfs2.
>
> Thanks. Looks good to me, I'll apply as is.
>
> BTW, what value is default for those users? And from users of some
> filesystems, it might be better to do in lower layer or VFS?
The situation is the following:
As of 2.6.32-rc7:
- btrfs needs the discard option to enable trim, it's off by default
- gfs2 needs the discard option to enable trim, it's off by default
- ext4 does discard by default, no option to disable
- fat does discard by default, no option to disable
- the swap code does discard by default, no option to disable
Eric has a patch for ext4 to implement the btrfs/gfs2 semantics, and
this is the one for fat. A discussion is ongoing about swap.
I don't think moving block specific options is a good idea to do in the
VFS. The other option would be to disable it in the block layer, but
that's not alwas intuitive.
next prev parent reply other threads:[~2009-11-18 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 17:08 [PATCH] fat: make discard a mount option Christoph Hellwig
2009-11-18 18:38 ` OGAWA Hirofumi
2009-11-18 18:53 ` Christoph Hellwig [this message]
2009-11-18 19:09 ` OGAWA Hirofumi
2009-11-18 19:15 ` Christoph Hellwig
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=20091118185358.GA29399@lst.de \
--to=hch@lst.de \
--cc=hirofumi@mail.parknet.co.jp \
--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).