From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Chris Mason <mason@suse.com>, reiserfs-list@namesys.com
Subject: Re: [PATCH] various allocator optimizations
Date: Wed, 12 Mar 2003 22:22:49 +0300 [thread overview]
Message-ID: <3E6F8909.7080805@namesys.com> (raw)
In-Reply-To: <20030312171718.C2128@namesys.com>
Oleg Drokin wrote:
>Hello!
>
>On Wed, Mar 12, 2003 at 05:08:21PM +0300, Hans Reiser wrote:
>
>
>>>>>Right, I missed the hint->search_start = bh->b_blocknr for when we don't
>>>>>find an indirect item.
>>>>>This is better, so the search will start from the bh with the stat data
>>>>>for a new file, but it depends on the last path element being in a good
>>>>>position relative to the rest of the files in the directory.
>>>>>
>>>>>
>>>>Where other than near the stat data do you propose?
>>>>
>>>>
>>>The permanent problem is that metadata may move inside of the tree from one
>>>block to another.
>>>So after some time, the blockin which stat data was inserted may move away
>>>from
>>>optimal file location.
>>>
>>>
>>Sounds like you need a repacker and allocate on flush....
>>
>>
>
>True for repacker. I do not see for allocate on flush will help.
>I see how relocate on flush may help ;)
>
>Bye,
> Oleg
>
>
>
>
If you don't allocate it until flush, you don't need to reallocate at
flush time...;-)
--
Hans
next prev parent reply other threads:[~2003-03-12 19:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 16:34 [PATCH] various allocator optimizations Chris Mason
2003-03-11 16:42 ` Oleg Drokin
2003-03-11 17:32 ` Chris Mason
2003-03-11 18:04 ` Oleg Drokin
2003-03-11 19:00 ` Chris Mason
2003-03-11 21:51 ` Hans Reiser
2003-03-11 21:42 ` Hans Reiser
2003-03-11 22:25 ` Chris Mason
2003-03-11 22:39 ` Anders Widman
2003-03-11 22:54 ` Hans Reiser
2003-03-11 23:19 ` Anders Widman
2003-03-12 7:15 ` Oleg Drokin
2003-03-11 22:46 ` Hans Reiser
2003-03-12 1:48 ` Chris Mason
2003-03-12 7:12 ` Oleg Drokin
2003-03-12 13:31 ` Chris Mason
2003-03-12 14:00 ` Hans Reiser
2003-03-12 14:05 ` Oleg Drokin
2003-03-12 14:08 ` Hans Reiser
2003-03-12 14:17 ` Oleg Drokin
2003-03-12 19:22 ` Hans Reiser [this message]
2003-03-13 6:11 ` Oleg Drokin
2003-03-13 12:06 ` Hans Reiser
2003-03-13 12:10 ` Oleg Drokin
2003-03-12 11:12 ` Hans Reiser
2003-03-12 13:35 ` Chris Mason
2003-03-12 14:03 ` Hans Reiser
2003-03-12 7:14 ` Oleg Drokin
2003-03-12 19:57 ` Chris Mason
2003-03-12 20:51 ` Hans Reiser
2003-03-13 15:59 ` Chris Mason
2003-03-14 0:15 ` Hans Reiser
2003-03-14 1:34 ` Chris Mason
2003-03-14 10:26 ` Hans Reiser
2003-03-14 13:51 ` Chris Mason
2003-03-14 18:59 ` Hans Reiser
2003-03-14 20:40 ` Chris Mason
2003-03-14 13:59 ` Manuel Krause
2003-03-14 14:10 ` Chris Mason
2003-03-16 16:25 ` Anders Widman
2003-08-18 16:15 ` Hans Reiser
2003-08-18 16:20 ` Yury Umanets
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=3E6F8909.7080805@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.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 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.