public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Just Marc <marc@corky.net>
To: David Chinner <dgc@sgi.com>
Cc: Barry Naujok <bnaujok@sgi.com>, xfs@oss.sgi.com
Subject: Re: xfs_fsr, performance related tweaks
Date: Fri, 29 Jun 2007 08:39:02 +0100	[thread overview]
Message-ID: <4684B716.6030601@corky.net> (raw)
In-Reply-To: <20070629074114.GS31489@sgi.com>

I agree with you.  But what about files it works on, heavily, then 
decides they can't be defragged further? then it tries to defrag them 
again and again and again.  And that's the end of my story.


David Chinner wrote:
> 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.
>
> Cheers,
>
> Dave.
>   

  reply	other threads:[~2007-06-29  7:46 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 [this message]
2007-06-30 17:17               ` Eric Sandeen
2007-07-01 22:43                 ` David Chinner
  -- 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=4684B716.6030601@corky.net \
    --to=marc@corky.net \
    --cc=bnaujok@sgi.com \
    --cc=dgc@sgi.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