From: "JP Howard" <jh_lists@fastmail.fm>
To: Edward Shishkin <edward@namesys.com>,
Andreas Dilger <adilger@clusterfs.com>,
ReiserFS List <reiserfs-list@namesys.com>,
Oleg Drokin <green@namesys.com>
Subject: Re: External journals and NVRAM devices
Date: Fri, 1 Nov 2002 21:37:03 UT [thread overview]
Message-ID: <20021101213703.D142A50D503@server5.fastmail.fm> (raw)
On Sat, 02 Nov 2002 00:58:40 +0300, "Edward Shishkin"
<edward@namesys.com> said:
> > > ----
> > > Blocksize: 4096
> > > <...>
> > > Journal parameters:
> > > <...>
> > > Size 8193 blocks (including 1 for journal header) (first block
> > > 18)
> > > ----
> > >
> > > So my journal is only 32k?
> >
> > Yes. Standard journal can be only 32K.
>
> Sorry, 32M!
>
Apologies to all for my lack of reading comprehension. Yes, of course
that shows 32M...
When the 2.4.20 journal-size patches are out I'll try and do some
benchmarking with larger journals on NVRAM devices. We use Cyrus IMAPd
which is very fsync intensive, so I expect an NVRAM journal may make a
big difference...
next reply other threads:[~2002-11-01 21:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 21:37 JP Howard [this message]
2002-11-04 13:16 ` External journals and NVRAM devices Chris Mason
2002-11-05 21:23 ` reiser
2002-11-06 20:18 ` Andreas Dilger
2002-11-06 20:42 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-11-05 22:12 JP Howard
2002-11-01 20:38 JP Howard
2002-11-01 20:57 ` Valdis.Kletnieks
2002-11-01 21:57 ` Edward Shishkin
2002-11-01 21:58 ` Edward Shishkin
2002-11-01 7:29 JP Howard
2002-11-01 7:49 ` Serge Kolodeznyh
2002-11-01 15:33 ` Len Sorensen
2002-11-01 15:10 ` Edward Shishkin
2002-11-01 5:38 Jeremy Howard
2002-11-01 6:29 ` Andreas Dilger
2002-11-01 14:30 ` Edward Shishkin
2002-11-01 20:40 ` Hans Reiser
2002-11-01 21:45 ` Edward Shishkin
2002-11-01 20:41 ` Hans Reiser
2002-11-02 3:04 ` Andrew Clausen
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=20021101213703.D142A50D503@server5.fastmail.fm \
--to=jh_lists@fastmail.fm \
--cc=adilger@clusterfs.com \
--cc=edward@namesys.com \
--cc=green@namesys.com \
--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.