From: Matthew Wilcox <matthew@wil.cx>
To: "Knight, Frederick" <Frederick.Knight@netapp.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
ricwheeler@gmail.com, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Thin device provisioning
Date: Sat, 9 Aug 2008 10:45:35 -0600 [thread overview]
Message-ID: <20080809164535.GK8618@parisc-linux.org> (raw)
In-Reply-To: <AC32D7C72530234288643DD5F1435D53A80EC3@RTPMVEXC1-PRD.hq.netapp.com>
I've spoken with a few Linux filesystem people. They find it
significantly easier to send a single LBA/length pair at a time.
Modern filesystems try quite hard to keep fragmentation to a minimum, so
they don't expect a performance hit from sending multiple commands.
They're non-blocking writes, and the IO elevators can take care of
sending more important reads first.
On Fri, Aug 08, 2008 at 05:58:15PM -0400, Knight, Frederick wrote:
> Thank you for your input. Yes, this was discussed. Most filesystems do
> not create fully contiguous files, and therefore when a file is deleted,
> some number of discontiguous extents must be punched/discarded. This is
> the reason for the list of LBA/length pairs.
>
> The alternative is that the filesystem must create 1 unique request to
> the driver for each extent, and the driver must create 1 CDB for each
> extent, and the filesystem must then iterate through the entire file for
> each discontiguous range. It was felt that this would be a problem for
> filesystems and drivers to do this type of operation, and it was
> preferred to simply supply a list.
>
> Thanks again for the input,
>
> Fred Knight
> SAN Standards Technologist
> NetApp
>
>
>
> -----Original Message-----
> From: Matthew Wilcox [mailto:matthew@wil.cx]
> Sent: Friday, August 08, 2008 9:15 AM
> To: Knight, Frederick
> Cc: David Woodhouse; ricwheeler@gmail.com
> Subject: Thin device provisioning
>
> * From the T10 Reflector (t10@t10.org), posted by:
> * Matthew Wilcox <matthew@wil.cx>
> *
> Good morning Fred,
>
> I've been looking at your 08-149r0.pdf with a view to using the 'PUNCH'
> command to implement the Linux 'DISCARD' command. It's a little
> over-specified for what we need and this causes the implementation to be
> a little more complex than I would like. The excess capability is the
> ability to do multiple punches in a single command. Do you really need
> to be able to add/remove lots of ranges atomically, or could you use a
> command specified like this:
>
> 0 0x9F
> 1 service action
> 2-9 LBA
> 10-13 length
> 14 reserved
> 15 control
>
> and send one command for each range?
>
> Apologies if this has already been covered in a T10 discussion; I'm not
> a member and though I've searched the archives, I may have missed a
> discussion.
>
> --
> Intel are signing my paycheques ... these opinions are still mine "Bill,
> look, we understand that you're interested in selling us this operating
> system, but compare it to ours. We can't possibly take such a
> retrograde step."
>
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo@t10.org
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next parent reply other threads:[~2008-08-09 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200808081714.m78HEMkA026466@coles02.co.lsil.com>
[not found] ` <AC32D7C72530234288643DD5F1435D53A80EC3@RTPMVEXC1-PRD.hq.netapp.com>
2008-08-09 16:45 ` Matthew Wilcox [this message]
2008-08-09 17:12 ` Thin device provisioning Knight, Frederick
2008-08-12 18:56 ` David Woodhouse
2008-08-12 20:38 ` Knight, Frederick
2008-08-12 23:21 ` Matthew Wilcox
2008-08-13 16:50 ` Alan D. Brunelle
2008-08-13 17:04 ` David Woodhouse
2008-08-10 0:50 ` Jamie Lokier
2008-08-10 3:51 ` 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=20080809164535.GK8618@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Frederick.Knight@netapp.com \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ricwheeler@gmail.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