[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1250779356.5533.15.camel@mulgrave.site>
Date: Thu, 20 Aug 2009 08:42:36 -0600
From: James Bottomley <James.Bottomley@...e.de>
To: Mark Lord <liml@....ca>
Cc: Ric Wheeler <rwheeler@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Christoph Hellwig <hch@...radead.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
xfs@....sgi.com, linux-fsdevel@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
jens.axboe@...cle.com,
IDE/ATA development list <linux-ide@...r.kernel.org>,
Neil Brown <neilb@...e.de>
Subject: Re: [PATCH, RFC] xfs: batched discard support
On Thu, 2009-08-20 at 10:38 -0400, Mark Lord wrote:
> Would it still be okay to do the TRIMs when the entire parity stripe
> (across all members) is being discarded? (As opposed to just partial
> data there being dropped)
Not really. The problem is that array verification is done at the block
level not the fs level (although, I suppose, we could change that). So
a fully discarded stripe still has to verify OK (as in what's read for
the parity must match what's read for the data). All of this is the
reason for the TPRZ bit for SCSI UNMAP ... and why WRITE_SAME is also
under consideration for discards in T10.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists