All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Chris Dukes <pakrat@www.uk.linux.org>, Spam <spam@tnonline.net>,
	reiserfs-list@namesys.com
Subject: flush earlier?  (was Re: Congratulations! we have got hash function screwed up)
Date: Fri, 07 Jan 2005 17:27:29 -0600	[thread overview]
Message-ID: <41DF1AE1.8090306@slaphack.com> (raw)
In-Reply-To: <41DEC53A.40403@namesys.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans Reiser wrote:
| Chris Dukes wrote:
|
|>
|>
|> All filesystems will fail or suffer degraded performance under
|> certain conditions, you need to determine what conditions are acceptable
|> for your data.
|>
|>
|>
| and each generation of software reduces the extent of such conditions.
| Reiser4 fixes this problem cleanly.

I think Reiser4's degraded performance condition is when it gets lots of
RAM.  First, a disclaimer -- I don't have the latest reiser4 patch.  But
in all versions of the FS, I've found that if I'm ever trying to do
anything when reiser finally decides to flush to disk, basically my
whole system is locked up.  I haven't tested, but I think this would
actually be worse with more RAM, because it would be longer until the
flush was forced, so each flush would take longer.

What is needed is some sort of estimator or estimate.  An estimator
would be something that would flush when, based on recent fs load, it
was reasonable to expect that RAM would fill up just as the flush was
completing.  An estimate would be to flush if a certain percentage of
RAM was full, and to go to synchronous mode if memory usage didn't go
back below that percentage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQd8a4HgHNmZLgCUhAQKb+A//fps5uIUtnfrHGe0y3itGbggWGkDqV80O
MPlLDqmlyMRWAGij5f5F345OU7GBi7VVCkgXMJbemO7TJ82Yr8OQXPO1Ywrt1rL5
bdPej6rZD7RW7+2DRlT78XdvP2ZbqKQNjvIlmLvQIziGk2BfGxwzxt1P5vztIvfE
HtqiP9ImSbxFkjRjZmdeQC8koyEK0vqYeasRma2pC1ZsABXxRHdRPnm/OT1gZc5D
YAYqyHCcs+RFr6+KYs9TSh4H5pNcHq1kYUEcoNFI0ubMSnNK+DvlrhBPhi5fkxPT
8D86nvphYFn7gKob1A9DZzKQz0qFcbhY35KW8g4hwHUrAyQWQtOU5sh+eIF0hV+j
LRhI6Ao6lgSAyq/GuxVwZ64emiM70JvoRNDLt4YVs4VDWnTcarhUNCikEUjvSCqj
Ux2RWI+6YILFso1D0Zl+4J0hkSxZPurzvRGL9TWT3Gwkdlyfk77jRbgfvZ5oy2aC
Q4gv5h/j+7AngfzlYY8n20zlocGoW8GEpaSgWa4VimTwAuHYEoDMu0TdlHLZzMB6
u2CBoYy7brCaxUpaV7np5E/rfEPcccINVgea0/dVhvkVGjyMQHb8msyX1r4IXRRC
jVxP2veoyxsyTTmcOCAViF6Epe4fVIhTnafH7hVmcWEk0Vt+aHSbAJtYK9oFTz7E
RX0WHi9z4fs=
=UeYu
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2005-01-07 23:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 22:12 Congratulations! we have got hash function screwed up Lehmann 
2004-12-29 18:55 ` Stefan Traby
2004-12-29 21:04   ` Lehmann 
2004-12-29 21:05   ` Hans Reiser
2004-12-29 21:43     ` Lehmann 
2004-12-29 21:46       ` Christian Iversen
2004-12-29 22:27         ` Lehmann 
2004-12-30  2:05       ` Hans Reiser
2004-12-30 10:22         ` Matthias Andree
2004-12-30 17:02         ` Lehmann 
2005-01-06 12:45 ` Alex Zarochentsev
2005-01-06 14:27   ` Lehmann 
2005-01-06 15:56     ` Hans Reiser
2005-01-06 16:13       ` Spam
2005-01-06 16:26         ` Chris Dukes
2005-01-06 16:29           ` Spam
2005-01-06 16:56             ` Chris Dukes
2005-01-07 17:22           ` Hans Reiser
2005-01-07 17:28             ` Chris Dukes
2005-01-07 23:27             ` David Masover [this message]
2005-01-07 23:52               ` flush earlier? (was Re: Congratulations! we have got hash function screwed up) Hans Reiser
2005-01-08  5:03                 ` David Masover
2005-01-08 20:48                   ` Hans Reiser
2005-01-09 23:26                     ` David Masover
2005-01-06 18:55     ` Congratulations! we have got hash function screwed up Edward Shishkin
2005-01-07 17:26       ` Lehmann 

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=41DF1AE1.8090306@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=pakrat@www.uk.linux.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=spam@tnonline.net \
    /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.