public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
	Lukas Czerner <lczerner@redhat.com>
Subject: Re: xfs: add FITRIM support
Date: Thu, 6 Jan 2011 09:10:29 +0100	[thread overview]
Message-ID: <201101060910.34534@zmi.at> (raw)
In-Reply-To: <20110105225039.GD8322@dastard>


[-- Attachment #1.1: Type: Text/Plain, Size: 1762 bytes --]

On Mittwoch, 5. Januar 2011 Dave Chinner wrote:
> No state or additional on-disk
> structures are needed for xfs_fsr to do it's work....

That's not exactly the same - once you defraged a file, you know it's 
done, and can skip it next time. But you dont know if the (free) space 
between block 0 and 20 on disk has been rewritten since the last trim 
run or not used at all, so you'd have to do it all again.
 
> The background trim is intended to enable even the slowest of
> devices to be trimmed over time, while introducing as little runtime
> overhead and complexity as possible. Hence adding complexity and
> runtime overhead to optimise background trimming tends to defeat the
> primary design goal....

It would be interesting to have real world numbers to see what's "best". 
I'd imagine a normal file or web server to store tons of files that are 
mostly read-only, while 5% of it a used a lot, as well as lots of temp 
files. For this, knowing what's been used would be great.

Also, I'm thinking of a NetApp storage, that has been setup to run 
deduplication on Sunday. It's best to run trim on Saturday and it should 
be finished before Sunday. For big storages that might be not easy to 
finish, if all disk space has to be freed explicitly.

And wouldn't it still be cheaper to keep a "written bmap" than to run 
over the full space of a (big) disk? I'd say depends on the workload.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
// 
// Haus zu verkaufen: http://zmi.at/langegg/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-01-06  8:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 11:23 xfs: add FITRIM support Christoph Hellwig
2010-12-22 21:41 ` Alex Elder
2010-12-28 16:09   ` Christoph Hellwig
2011-01-03 10:49     ` Lukas Czerner
2010-12-23  1:44 ` Dave Chinner
2010-12-30 11:41   ` Christoph Hellwig
2011-01-03 10:57     ` Lukas Czerner
2011-01-03 23:25       ` Dave Chinner
2011-01-05 10:21         ` Lukas Czerner
2011-01-05 22:07           ` Michael Monnerie
2011-01-05 22:50             ` Dave Chinner
2011-01-06  8:10               ` Michael Monnerie [this message]
2011-01-06  8:33                 ` Lukas Czerner
2011-01-06  8:40                   ` Lukas Czerner
2011-01-06  9:17                 ` Dave Chinner
2011-01-06 16:50                   ` Michael Monnerie
2011-01-06 18:10                     ` Christoph Hellwig
2011-01-06 18:08               ` Christoph Hellwig
2011-01-06 18:06             ` 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=201101060910.34534@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=hch@infradead.org \
    --cc=lczerner@redhat.com \
    --cc=xfs@oss.sgi.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