public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: David Chinner <dgc@sgi.com>, Just Marc <marc@corky.net>,
	Barry Naujok <bnaujok@sgi.com>,
	xfs@oss.sgi.com
Subject: Re: xfs_fsr, performance related tweaks
Date: Mon, 2 Jul 2007 08:43:39 +1000	[thread overview]
Message-ID: <20070701224339.GV31489@sgi.com> (raw)
In-Reply-To: <46869029.3040704@sandeen.net>

On Sat, Jun 30, 2007 at 01:17:29PM -0400, Eric Sandeen wrote:
> David Chinner wrote:
> > On Fri, Jun 29, 2007 at 08:16:28AM +0100, Just Marc wrote:
> >> David,
> >>
> >> In my first post I already said something like that can be done but it's 
> >> just an ugly hack.   Don't you think it would best be handled cleanly 
> >> and correctly by fsr itself?
> > 
> > No, I don't - if you want files not to be defragmented, then you
> > have to set the flags yourself in some way. You have a specific need
> > that can be solved by some scripting to describe your defrag/no
> > defrag policy. xfs_fsr has no place is setting defrag policy; it's
> > function is simply to find and defrag files.
> 
> I wouldn't mind seeing a way to tell fsr to not worry about defragging
> some files based on current layout; say if the avg extent in the file is
> > 100MB, or > 1G, don't bother... if today you have a 4.7G DVD iso image
> in 3 extents (not bad) fsr will try to "fix" it for you right?

That could be easily done with command line options, I think. Define
the minimum extent length or number of extents we want files to have
and ignore those that are outside that criteria.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-07-01 22:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 12:47 xfs_fsr, performance related tweaks Just Marc
2007-06-28 20:38 ` Eric Sandeen
2007-06-29  0:52   ` Andi Kleen
2007-06-29  6:21   ` Just Marc
2007-06-29  6:41     ` Barry Naujok
2007-06-29  6:41       ` Just Marc
2007-06-29  7:08         ` David Chinner
2007-06-29  7:16           ` Just Marc
2007-06-29  7:33             ` Nathan Scott
2007-06-29  7:41             ` David Chinner
2007-06-29  7:39               ` Just Marc
2007-06-30 17:17               ` Eric Sandeen
2007-07-01 22:43                 ` David Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-28 12:47 Just Marc
2007-06-29  0:12 ` Nathan Scott
2007-06-29  6:31   ` Just Marc
2007-06-29  8:13     ` Andi Kleen
2007-06-29  8:23       ` Just Marc
2007-06-29  8:58         ` Andi Kleen

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=20070701224339.GV31489@sgi.com \
    --to=dgc@sgi.com \
    --cc=bnaujok@sgi.com \
    --cc=marc@corky.net \
    --cc=sandeen@sandeen.net \
    --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