public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Tejun Heo <teheo@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Piggin <npiggin@suse.de>, Jens Axboe <jens.axboe@oracle.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>, Dongjun Shin <djshin90@gmail.com>,
	chris.mason@oracle.com
Subject: Re: about TRIM/DISCARD support and barriers
Date: Sun, 23 Nov 2008 13:39:44 +0000	[thread overview]
Message-ID: <1227447584.4901.405.camel@macbook.infradead.org> (raw)
In-Reply-To: <20081123123514.GI5707@parisc-linux.org>

On Sun, 2008-11-23 at 05:35 -0700, Matthew Wilcox wrote:
> The current VFAT filesystem implements DISCARD. 

As does btrfs. I think I posted ext2 patches a little while ago too? Or
someone else did. Did they get merged?

>  Here's the patch I've
> been testing -- it's not right; it causes SSDs from two different vendors
> to hang.  I'm waiting for a free slot on the SATA protocol analyser to
> figure out what's we're doing wrong.
> 
> Note that the SCSI UNMAP command does not yet have an official number,
> so this patch cannot yet be applied (... how much longer until ATA is no
> longer part of SCSI?)
> 
> We don't attempt to put non-contiguous ranges into a single TRIM yet.

We don't even merge contiguous ranges -- I still need to fix the
elevators to stop writes crossing writes, before we can stop discards
from also being barriers. (Discards are just writes, for the purpose of
that conversation).

> We currently assume all SCSI devices support UNMAP instead of checking
> the feature flag (because last time I looked, I couldn't tell what flag
> I was supposed to check).  Once we do that, I need to set that flag in
> libata-scsi depending on the support for the TRIM bit in the identify
> command.

The code in drivers/ide does check the feature, although I'm not 100%
sure I got that part right.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation


  reply	other threads:[~2008-11-23 13:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23  4:46 about TRIM/DISCARD support and barriers Tejun Heo
2008-11-23  7:11 ` Tejun Heo
2008-11-23  7:57   ` Tejun Heo
2008-11-24  5:40     ` Dongjun Shin
2008-11-24  5:45       ` Tejun Heo
2008-11-24  5:57       ` James Bottomley
2008-11-23 12:35   ` Matthew Wilcox
2008-11-23 13:39     ` David Woodhouse [this message]
2008-11-23 22:52       ` James Bottomley
2008-11-24  9:03         ` David Woodhouse
2008-11-24 18:42           ` James Bottomley
2008-11-24 18:52             ` David Woodhouse
2008-11-24 18:57               ` Jens Axboe
2008-11-24 19:08                 ` James Bottomley
2008-11-25  9:16                   ` Jens Axboe
2008-11-24 19:09               ` James Bottomley
2008-11-25  3:28           ` Matthew Wilcox
2008-11-25  9:15             ` Jens Axboe
2008-11-24  3:01       ` Theodore Tso

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=1227447584.4901.405.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=chris.mason@oracle.com \
    --cc=djshin90@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=npiggin@suse.de \
    --cc=teheo@suse.de \
    /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