All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter" <sw98234-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org
Subject: Re: Relocating files for faster boot/start-up on reiser(fs/4)
Date: Wed, 13 Sep 2006 21:10:44 +0000 (UTC)	[thread overview]
Message-ID: <ee9s4k$f58$1@sea.gmane.org> (raw)
In-Reply-To: 200609131451.42474.lists@qutek.net

On Wed, 13 Sep 2006 14:51:39 -0600, Quinn Harris wrote:
> 
> Thoughts?
>

Yes. Why on earth would you do this? By copying the files and renaming and
hardlinking them is nothing a sysadmin would ever do. Just by copying you
are allowing reiser to optimize the dir. You're trying to duplicate what a
tree-based design does automatically. Moreover, remember that reiser packs
files into clusters so that you may read more than just your one file from
time to time which could end up adding time to your test.

If reiser needs speedup it certainly won't be done by renaming files!

JM$0.02

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357


  reply	other threads:[~2006-09-13 21:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 20:51 Relocating files for faster boot/start-up on reiser(fs/4) Quinn Harris
2006-09-13 21:10 ` Peter [this message]
2006-09-14  3:10   ` Quinn Harris
2006-09-14 19:55     ` David Masover
2006-09-14 22:09       ` Quinn Harris
2006-09-14 22:23         ` David Masover
2006-09-15  5:15           ` Toby Thain
2006-09-15 21:20             ` Quinn Harris
2006-09-15 22:27               ` David Masover
2006-09-16  0:01                 ` Quinn Harris
2006-09-16  8:59                   ` David Masover
2006-09-18  9:36               ` PFC
2006-09-18 22:32                 ` Quinn Harris
2006-09-14 14:01   ` cmaurand

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='ee9s4k$f58$1@sea.gmane.org' \
    --to=sw98234-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
    --cc=reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.