From: David Masover <ninja@slaphack.com>
To: Christian Iversen <chrivers@iversen-net.dk>
Cc: reiserfs-list@namesys.com
Subject: Re: Plugin for corruption resistance?
Date: Thu, 17 Feb 2005 21:43:08 -0600 [thread overview]
Message-ID: <4215644C.4000602@slaphack.com> (raw)
In-Reply-To: <200502171153.43403.chrivers@iversen-net.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Iversen wrote:
| On Thursday 17 February 2005 05:10, David Masover wrote:
|
|>Adam wrote:
|>| Hans Reiser <reiser <at> namesys.com> writes:
|>|>Its on the legitimate wish list, if someone wants to code it, let me
|>|> know.
|>|
|>| Hans, does this mean that you think that this type of functionality
|>
|>should be
|>
|>| implemented as a Reiser4 plugin and therefore in kernelspace? Why
|>
|>wouldn't this
|>
|>| be better implemented in userspace via a daemon that is notified of file
|>| modification via dnotify/inotify?
|>
|>Because dnotify/inotify don't scale. I don't think they lock on event,
|>either, whereas a plugin could guarentee that the hash was up-to-date
|>(no race conditions).
|>
|>We've been over this before. There's a reason reiser4 and its plugins
|>are in kernel space, and not in something like Fuse.
|
|
| And, surely, updating a hash value when 1 byte changes in a gigabyte
file,
| would be much faster from kernel space where you can actually see the
| changeset?
Wouldn't it be sane to just export the changeset to userland?
This way is easier, though. But I was thinking about accessing the
file. I don't know of any hashes that can be easily updated from part
of the file, unless you're hashing only pieces of the file in the first
place, but it'd be nice to not bother hashing at all until the hash is
needed, especially if we are hashing the whole file.
Plus, there's the race condition thing. Definitely a lot of reasons to
put more stuff in the kernel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQhVkS3gHNmZLgCUhAQIMNA/+IgaEx9p3bceATrrYDEweAB+N4K98dFyM
BgDAtxFS2vzaw6lsF9vtEiHEuhvp5raCAhxcoEO1KgRh21Yc6cR+Yu5FaRc7BV4n
WleJtNk521XFwUsmQXs5nYYHzfNlfJbQax9RBqX4IllbXbHX6YUHDAof/Zy8M4MJ
Wytp10igur9QVcqXSeEYoRbYHXS3MRyT3cIl6Y1VXAdZRYu/ItlLf0ItRPkRyfB7
1yVK4kOaR4c6U95gaHL0S08tLddtiep+9XIAJ+JXdhnP8yfEH43ItoM/KxrGSc/K
PWcgIDicYek6kWWNb8H5dTYIknaW8fYwStuoBdfaLt/9aGO00O4sNmg97skW8H2q
+87d22MTiCFtbHyYnD5cV6EzKe+IdUqcTaISOMbctltQmBsPcQjeAlU+BmaLbzEF
sN91egbv/iuirroO1/OzCCQrihE6u8/9tK6LO2Y+LGO2N+ZpB10ZHaGa8uHqMFy1
w19r9XcTIJHo+mjuWhM4hnRrna8cwsCepf++tyKE26ZD3iPPaUzB8h+U81R+59y0
TXNLKLCfJfuOBs4IK2MgmcSkvxEpzBos3vJJdlvA3s4aMz6ZAP8vp5Wgj/BvMrxj
QhFdy/IPCdDLHc5EO3rOZo3b8e/GZcfxgOJ54nuMMzk0xFrlIbtBtYCBU41o9jiq
yP/8bcQ4cqY=
=UEM3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-02-18 3:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 18:58 Plugin for corruption resistance? Gregory Maxwell
2005-02-11 20:39 ` Jake Maciejewski
2005-02-11 20:53 ` Tom Vier
2005-02-12 5:19 ` David Masover
2005-02-13 3:48 ` Esben Stien
2005-02-14 2:01 ` Reiser 4 Apple Michael James
2005-02-14 18:49 ` Hans Reiser
2005-02-14 17:45 ` Plugin for corruption resistance? Hans Reiser
2005-02-15 20:42 ` Adam
2005-02-17 4:10 ` David Masover
2005-02-17 10:53 ` Christian Iversen
2005-02-18 3:43 ` David Masover [this message]
2005-02-18 4:28 ` Valdis.Kletnieks
2005-02-18 13:36 ` Gregory Maxwell
2005-02-18 22:09 ` Valdis.Kletnieks
2005-02-19 3:28 ` Gregory Maxwell
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=4215644C.4000602@slaphack.com \
--to=ninja@slaphack.com \
--cc=chrivers@iversen-net.dk \
--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.