From: Hans Reiser <reiser@namesys.com>
To: Hendrik Visage <hvisage@envisage.co.za>
Cc: reiserfs-list@namesys.com
Subject: Re: early flushing of data
Date: Mon, 12 Aug 2002 18:14:51 +0400 [thread overview]
Message-ID: <3D57C2DB.8020204@namesys.com> (raw)
In-Reply-To: 20020812140529.GY282@hvs.envisage.co.za
Hendrik Visage wrote:
>On Mon, Aug 12, 2002 at 05:52:35PM +0400, Hans Reiser wrote:
>
>
>>I just thought that discussion of this might interest the list.
>>
>>It is interesting to consider whether one should flush dirty nodes to
>>disk with only a small delay after they are modified, or keep them in
>>cache for a longer time.
>>
>>
>[snip]
>
>
>>Your thoughts are welcome.
>>
>>
>
>Being in love with buttons-an-dials, I'd vote for a configurable flush
>setting.
>
>I have the case were one email server (basically a hop in the queue) would do
>well with the longer flushes as the data wouldn't be that long before it's
>shipped out again (given no failure conditions), while I have others which
>I'd like to have it to disk ASAP as it'll be taking awhile before it get's
>moved along again.
>
>Thus a configurable setting (would love/prefer a per mount setting ie.
>one for my log mount, and the other for the email mounts etc.) would
>be nice.
>
>
>
>
>
Yes, but what should the default be (remember that 97% of users or more
won't change the default)?
--
Hans
next prev parent reply other threads:[~2002-08-12 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 13:52 early flushing of data Hans Reiser
2002-08-12 14:05 ` Hendrik Visage
2002-08-12 14:14 ` Hans Reiser [this message]
2002-08-12 14:24 ` Hendrik Visage
2002-08-12 14:21 ` Opportunistic " Xuan Baldauf
2002-08-12 14:32 ` Hans 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=3D57C2DB.8020204@namesys.com \
--to=reiser@namesys.com \
--cc=hvisage@envisage.co.za \
--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.