public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tom Reinhart" <rhino_tom@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply
Date: Wed, 06 Nov 2002 10:37:46 -0800	[thread overview]
Message-ID: <F156TOqVPo2HJS3F7il00005647@hotmail.com> (raw)

I would think the default should be a lot more conservative than that, 
probably closer to 30 seconds.  Much better to default to safety, and allow 
knowledgable users to tradeoff for performance if they can live with the 
risks.

Tom


>>There is also a longer PhD thesis by her. 10 minutes is about as much
>>work as I personally am willing to lose and try to remember. Avoiding
>>75% of writes instead of 20% is a substantial performance gain worth
>>paying a cost for. Unfortunately it is not easy to say if it is worth
>>that much cost, but I suspect it is. An approach we are exploring is
>>for blocks to reach disk earlier than that if the device is not
>>congested, on the grounds that if not much IO is occuring, then
>performance is not important.
>
>Assuming your 10 minutes are just a default and tunable by sysctl I
>hardly can see any problems at all. Paranoid people can set it to
>make any tradeoff between performance and speed they'd like including
>setting it to 0, no?




_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail


             reply	other threads:[~2002-11-06 18:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 18:37 Tom Reinhart [this message]
     [not found] <877555917@toto.iv>
2002-11-05 23:09 ` [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply Peter Chubb
2002-11-06  1:33   ` reiser
2002-11-06 14:25     ` Daniel Egger
2002-11-07 17:19       ` Pavel Machek
2002-11-07 16:58     ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 21:23 [BK][PATCH] Reiser4, will double Linux FS performance, please apply Hans Reiser
2002-10-31 22:34 ` Dieter Nützel
2002-10-31 22:47   ` Hans Reiser
2002-11-01  1:17     ` [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply Andrew Morton
2002-11-01  1:27       ` Andrew Morton
2002-11-05 21:39       ` reiser
2002-11-01  1:27 ` Hans Reiser
2002-11-01  1:33   ` Andrew Morton
2002-11-01  1:44     ` Dieter Nützel
2002-11-01  4:36     ` Linus Torvalds
2002-11-01 10:59       ` Nikita Danilov
2002-11-01  1:55 ` Hans Reiser
2002-11-01 10:23   ` Tomas Szepe
2002-11-01 17:19     ` Alexander Zarochentcev
2002-11-02 13:24       ` Tomas Szepe
2002-11-04 11:00         ` Nikita Danilov
2002-11-04 19:56           ` Andreas Dilger
2002-11-02 13:38       ` Tomas Szepe
2002-11-04 12:02         ` Nikita Danilov
2002-11-04 17:10           ` Tomas Szepe
2002-11-04 17:53             ` Nikita Danilov
2002-11-04 18:10               ` Tomas Szepe
2002-11-05  7:30 ` reiser
2002-11-05  8:28   ` Alexander Zarochentcev
2002-11-05  9:29   ` Andreas Dilger
2002-11-05  9:59   ` Tomas Szepe
2002-11-05 10:08     ` Alexander Zarochentcev
2002-11-05 10:23       ` Tomas Szepe
2002-11-05 10:46     ` Nikita Danilov
2002-11-05  8:44 ` reiser
2002-11-05  8:49   ` Alexander Zarochentcev
2002-11-05 21:08 ` reiser

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=F156TOqVPo2HJS3F7il00005647@hotmail.com \
    --to=rhino_tom@hotmail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox