All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Shawn Rutledge <shawn.t.rutledge@gmail.com>
Cc: Hans Reiser <reiser@namesys.com>,
	"Vladimir V. Saveliev" <vs@namesys.com>,
	reiserfs-list@namesys.com
Subject: Re: where is the journal kept?
Date: Tue, 16 Aug 2005 17:30:12 -0500	[thread overview]
Message-ID: <430268F4.8020100@slaphack.com> (raw)
In-Reply-To: <d9a6586e05081613275071c00a@mail.gmail.com>

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

Shawn Rutledge wrote:
> On 8/16/05, Hans Reiser <reiser@namesys.com> wrote:
> 
>>Reiser4 does a very nice job of packing the tree tightly, which is
>>independent of seeks.  Ditto for compression plugin.
>>He merely needs to ignore some code, he is not harmed by it.  If he
>>wants to write a new block allocator, sure, why not, we have allocator
>>plugins yes?   His will just be simpler.....
> 
> 
> But the most important thing is to reduce the number of writes as low
> as possible.

Something Reiser4 does very well.  If you have enough RAM, it's possible
to avoid any reads/writes at all -- given enough RAM, it behaves as a
ramdisk, which is why I wish I knew how to tell Gentoo to *not* mount
tmpfs over /dev.

One other thing you might try is disabling the write-twice behavior.
Currently, if you've got a huge, fairly well-sorted file that you're
making lots of tiny writes to, such as a database, it makes sense to
write twice to keep the file from getting fragmented.  But,
fragmentation isn't nearly as much an issue on truly random-access
media, so you'd want the default small-file behavior to be used
everywhere -- first write the data to the new location, then atomically
update the pointer to it as you deallocate the old location.

Am I right about this?  I'm not feeling very lucid today...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQwJo9HgHNmZLgCUhAQK92BAAk68ZQsOMyS3TTKmu3//gkC+/RHzrNXey
UR2YxH+FdC7BDR3Py2Mmot3F7Ch5ykdT3gRzbMQ3vTQoRDlcmIVOuQ4VqfJ4vN2a
CVWVxc0X38fF7QVMoHnlwX6mRlr7PTd64BZEmYJ8cdDkPmAUrlCe0/+vLmorc2Oo
3Wwz3rtLotu+7Z4sjWvboqyXFoX8hvt0iSo+45UnQI7bNwdbWCpFZBTsbU9SsI4J
NnplO/IG1d5jQq+Vdmo7lL0XB+Zv71s9u0l/QNe5eahLNUfzghrTVTZSpJT/+h3b
xSPMy2xVurG7p2jp3Rg8sN0YMiAGaQtVr9yhvcinZnmVOY9HK272Epihg3eUHYIX
LiKkCLblLaUiwJs6DKSCoCsF3oWELH/SsYC31R4fSWEVehObRIoU/Kz4TRtOeA0G
SakH4s+Hiju4GPTL7AKaMMi2TbeZgGg7BlZof+zC5HgQf7d2t0/sb2613X0R5agH
tQyiX7PDg+zQr4KXC8Rb3kwwcgURMcAUWw6gcJ+hTbFrLtlkvK9k1VJNmllH7j8J
aYTsz3FCgGo5a7zq4iogFt7GgnHeTJ3ErxjohK0uE3J10l68DvVa3TqaanGXdhDK
pqhfduXM+pt8FLoXuHVkp1c4VpZMzj4WWKPNOhH+FTxCVJee6ZeMckV+9AUbZkkW
ja3lcplEEMM=
=B2OX
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-08-16 22:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 11:53 where is the journal kept? Payal Rathod
2005-08-15 12:25 ` Vladimir V. Saveliev
2005-08-15 12:50   ` Payal Rathod
2005-08-15 12:58     ` Vladimir V. Saveliev
2005-08-15 13:12       ` Pat Double
2005-08-15 14:26         ` Vladimir V. Saveliev
2005-08-15 15:52           ` David Masover
2005-08-15 16:19           ` Shawn Rutledge
2005-08-15 17:34             ` Vladimir V. Saveliev
2005-08-15 18:08               ` Shawn Rutledge
2005-08-16 19:59                 ` Hans Reiser
2005-08-16 20:27                   ` Shawn Rutledge
2005-08-16 22:30                     ` David Masover [this message]
2005-08-16 23:23                       ` Shawn Rutledge
2005-08-17  0:02                         ` David Masover
2005-08-17  0:47                           ` Shawn Rutledge
2005-08-17  5:51                       ` 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=430268F4.8020100@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=shawn.t.rutledge@gmail.com \
    --cc=vs@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.