From: Just Marc <marc@corky.net>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_fsr, performance related tweaks
Date: Fri, 29 Jun 2007 07:21:58 +0100 [thread overview]
Message-ID: <4684A506.4030705@corky.net> (raw)
In-Reply-To: <46841C60.5030207@sandeen.net>
Hi Eric,
In my particular case, and I'm sure for many other people, files that
are stored never change again until they deleted. I hinted that there
could be a command line switch to turn this functionality on, as it may
not be perfect for everyone's use cases.
If nobody likes this still, I would appreciate some hints on how to mark
files as no-defrag from within fsr itself given that I only have the
file descriptor ... A hack like looking up the descriptor in
/proc/self/fd should work, but is linux specific and is too hackish in
my opinion. I'd like to at least have a nice simple patch for my own uses.
Marc
Eric Sandeen wrote:
> Just Marc wrote:
>
>
>> 2. Files for which 'No improvement will be made' should also be marked
>> as no-defrag, this will avoid a ton of extra work in the future.
>>
>
> But... that file could drastically change in the future, no? Just
> because it can't be improved now doesn't necessarily mean that it should
> never be revisited on subsequent runs, does it?
>
> -Eric
>
>
>
next prev parent reply other threads:[~2007-06-29 6:29 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 [this message]
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
-- 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=4684A506.4030705@corky.net \
--to=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