From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Oleg Drokin <green@namesys.com>, reiserfs-list@namesys.com
Subject: Re: [PATCH] various allocator optimizations
Date: Wed, 12 Mar 2003 17:03:50 +0300 [thread overview]
Message-ID: <3E6F3E46.4030101@namesys.com> (raw)
In-Reply-To: <1047476132.8218.510.camel@tiny.suse.com>
Chris Mason wrote:
>On Wed, 2003-03-12 at 06:12, Hans Reiser wrote:
>
>
>
>>>I like the idea of a dynamic in-kernel fragmentation tool though, you
>>>mark a file as being in need of reallocation, and it happens before io
>>>or something (hand waving is fun).
>>>
>>>
>>>
>>You mean you like the allocate on flush we do in reiser4?
>>
>>Perhaps I should say only that for 80% of machines 80% of the files
>>never move during the course of a week.;-)
>>
>>allocate on flush will improve a lot of the cases, and an online
>>repacker will improve a lot of the ones that allocate on flush does not
>>improve.
>>
>>
>
>None of which solves the question of how do we lay things out on disk
>;-)
>
>-chris
>
>
>
>
>
>
Well, okay, so what are you proposing and what are your benchmarks?
This is an area where the algorithms are simple but their consequences
are just guesses until they are measured.
--
Hans
next prev parent reply other threads:[~2003-03-12 14:03 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
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 [this message]
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=3E6F3E46.4030101@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.