All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 features RFC - separate journal?
Date: Fri, 05 May 2006 11:57:06 -0700	[thread overview]
Message-ID: <445BA002.9080909@oracle.com> (raw)
In-Reply-To: <445B32E4.C8CD.0002.0@novell.com>

jbd is also asynch. That's not the issue. The issue is more the size of the
journal. The larger the journal, the lesser need to flush the journal.

In ocfs2, as each slot has a separate journal, there is a desire to 
limit the
journal size so as to make more space available to actual data. Also, as the
fs is clustered, flushes could be triggered by other nodes.

So, having a separate device makes sense. It adds complexity to the
configuration, but, that is to be expected. ;)

Paul Taysom wrote:
>  The performance you might gain from a separate journaling device will
> be very dependent on exactly how the journal is done.  On NSS, the
> Netware journaled file system, we ran experiments with the journal
> turned off (just didn't do the write) and found it had little impact on
> benchmarks like NetBench.  Part of the reason for this is that the
> journal writes were asynchronous to the main flow of the system.  Normal
> operations would normally not ever wait for journal writes.
>
> Paul
>  
> _______________________________________________
> Ocfs2- devel mailing list
> Ocfs2- devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2- devel
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>   

  parent reply	other threads:[~2006-05-05 18:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 18:35 [Ocfs2-devel] OCFS2 features RFC Mark Fasheh
2006-04-25 21:55 ` Christoph Hellwig
2006-04-25 22:24   ` Mark Fasheh
2006-04-26 16:50   ` Daniel Phillips
2006-04-26  4:11 ` Andi Kleen
2006-04-26 18:06   ` Mark Fasheh
2006-04-26 18:08     ` Andi Kleen
2006-04-26 18:34       ` Daniel Phillips
2006-04-27 20:25 ` Paul Taysom
2006-05-03 23:04 ` [Ocfs2-devel] OCFS2 features RFC - separate journal? Daniel Phillips
2006-05-04  0:29   ` Zach Brown
2006-05-04  0:46     ` Daniel Phillips
2006-05-04 20:56       ` Zach Brown
2006-05-04 20:59         ` Wim Coekaerts
2006-05-04 22:23         ` Daniel Phillips
2006-05-04 22:30           ` Mark Fasheh
2006-05-05  3:05             ` Daniel Phillips
2006-05-05 18:25               ` Mark Fasheh
2006-05-06  3:09                 ` Daniel Phillips
2006-05-05 17:12             ` Paul Taysom
2006-05-05 18:06               ` Daniel Phillips
2006-05-05 18:57               ` Sunil Mushran [this message]
2006-05-08 14:28             ` Paul Taysom
2006-05-08 17:43               ` Daniel Phillips
2006-05-08 18:00             ` Paul Taysom
2006-05-08 18:22               ` Daniel Phillips
2006-05-11 20:04 ` [Ocfs2-devel] OCFS2 features RFC Jeff Mahoney
2006-05-11 20:40   ` Paul Taysom
2006-05-11 20:55     ` Joel Becker
2006-05-11 21:16   ` Daniel Phillips
2006-05-17  1:44   ` Mark Fasheh
     [not found]     ` <446BBCF5.7040903@google.com>
     [not found]       ` <20060518024638.GY21588@ca-server1.us.oracle.com>
2006-05-19  0:35         ` Daniel Phillips
2006-05-19 15:16           ` J. Bruce Fields
2006-05-20  6:11           ` Mark Fasheh
2006-05-22 19:18             ` Daniel Phillips
2006-05-22 17:01     ` Paul Taysom

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=445BA002.9080909@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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.