From: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Hans Reiser <reiser@namesys.com>, Chris Mason <mason@suse.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Horrible ftruncate performance
Date: Wed, 23 Jul 2003 17:24:35 +0200 [thread overview]
Message-ID: <20030723172435.40f26438.philippe.gramoulle@mmania.com> (raw)
In-Reply-To: <200307231624.07610.Dieter.Nuetzel@hamburg.de>
Hello Dieter,
On Wed, 23 Jul 2003 16:24:07 +0200
Dieter Nützel <Dieter.Nuetzel@hamburg.de> wrote:
| > Extents are the proper fix for hole performance.
|
| OK.
|
| But V4 is for 2.5/2.6 only...
|
| What are our options?
Well, hopefully, 2.6 will be released around the same time that ReiserFS V4 will
have been through its debug period.
So your options is to wait until 2.6/V4 is out or pay Namesys enough so that it
looks interesting to fix this in V3. :)
Bye,
Philippe
next prev parent reply other threads:[~2003-07-23 15:24 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 3:23 Horrible ftruncate performance Szakacsits Szabolcs
2003-07-10 5:29 ` Oleg Drokin
2003-07-10 7:30 ` Szakacsits Szabolcs
2003-07-10 9:21 ` Oleg Drokin
2003-07-10 8:17 ` Szakacsits Szabolcs
2003-07-10 10:01 ` Oleg Drokin
2003-07-10 14:01 ` Szakacsits Szabolcs
2003-07-10 15:44 ` Oleg Drokin
2003-07-11 14:35 ` Dieter Nützel
2003-07-11 14:49 ` Oleg Drokin
2003-07-11 15:16 ` Dieter Nützel
2003-07-11 15:24 ` Oleg Drokin
2003-07-11 15:27 ` Dieter Nützel
2003-07-11 15:32 ` Oleg Drokin
2003-07-11 15:35 ` Dieter Nützel
2003-07-11 15:32 ` Dieter Nützel
2003-07-11 15:36 ` Marc-Christian Petersen
2003-07-11 15:36 ` Dieter Nützel
2003-07-11 15:38 ` Oleg Drokin
2003-07-11 15:34 ` Marc-Christian Petersen
2003-07-11 15:44 ` Oleg Drokin
2003-07-11 17:09 ` Chris Mason
2003-07-11 17:27 ` Dieter Nützel
2003-07-11 18:32 ` Chris Mason
2003-07-11 19:51 ` Dieter Nützel
2003-07-12 1:37 ` Szakacsits Szabolcs
2003-07-12 5:16 ` Carl-Daniel Hailfinger
2003-07-12 3:49 ` Szakacsits Szabolcs
2003-07-12 13:51 ` Dieter Nützel
2003-07-15 12:19 ` Szakacsits Szabolcs
2003-07-15 16:48 ` Dieter Nützel
2003-07-15 17:05 ` Oleg Drokin
2003-07-15 19:55 ` Dieter Nützel
2003-07-16 10:35 ` Oleg Drokin
2003-07-16 10:47 ` Dieter Nützel
2003-07-16 10:57 ` Oleg Drokin
2003-07-17 18:12 ` Dieter Nützel
2003-07-22 16:43 ` Hans Reiser
2003-07-22 16:50 ` Chris Mason
2003-07-22 18:09 ` Hans Reiser
2003-07-22 18:24 ` Chris Mason
2003-07-23 0:16 ` Oleg Drokin
2003-07-23 6:25 ` Hans Reiser
2003-07-23 5:49 ` Voicu Liviu
2003-07-23 7:32 ` Hans Reiser
2003-07-23 7:19 ` Voicu Liviu
2003-07-23 6:14 ` Hans Reiser
2003-07-23 14:38 ` Chris Mason
2003-07-23 14:55 ` Hans Reiser
2003-07-23 16:20 ` Chris Mason
2003-07-23 12:25 ` Dieter Nützel
2003-07-23 13:39 ` Hans Reiser
2003-07-23 13:46 ` Dieter Nützel
2003-07-23 13:52 ` Hans Reiser
2003-07-23 14:24 ` Dieter Nützel
2003-07-23 15:24 ` Philippe Gramoullé [this message]
2003-07-12 14:05 ` Dieter Nützel
2003-07-13 13:00 ` Oleg Drokin
2003-07-13 12:58 ` Oleg Drokin
2003-07-14 8:45 ` Hans Reiser
2003-07-13 13:03 ` Oleg Drokin
2003-07-15 11:51 ` Szakacsits Szabolcs
2003-07-15 13:51 ` Hans Reiser
2003-07-11 19:23 ` Philippe Gramoullé
2003-08-03 14:05 ` Hans Reiser
2003-08-04 13:41 ` Chris Mason
2003-07-11 14:27 ` Chris Mason
2003-07-11 14:32 ` Dieter Nützel
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=20030723172435.40f26438.philippe.gramoulle@mmania.com \
--to=philippe.gramoulle@mmania.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=mason@suse.com \
--cc=reiser@namesys.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.