All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@google.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 features RFC - separate journal?
Date: Mon, 08 May 2006 11:22:15 -0700	[thread overview]
Message-ID: <445F8C57.7000501@google.com> (raw)
In-Reply-To: <445F32A9.C8CD.0002.0@novell.com>

Paul Taysom wrote:
> Network Appliance has been very successful with exactly this
> architecture.
> Paul 

Perhaps alternative architectures exist that are just as good, if not
better?

Regards,

Daniel

>>>>Daniel Phillips <phillips@google.com> 05/08/06 11:43 am >>> 
> 
> Paul Taysom wrote:
> 
>>If I was worried about NFS performance, I'd rather use NVRAM as an
>>immediate reply disk drive.
> 
> 
> What makes you think that that is any faster than just having a fast
> journal on the filesystem?  It is certainly messier and adds two more
> data copies.  Plus it only helps NFS, what if there are other servers
> on the node?  And how do you maintain cache consistency with the data
> written to the NFS reply journal when it has been acknowledged but is
> not actually in the filesystem?
> 
> On a snapshot, the NFS reply journal would be one more thing that
> needs to be flushed, this is one more thing needing administration
> attention.
> 
> How much latency do you think is saved by a dedicated reply journal vs
> a fast filesystem journal?  I doubt it is as much as you suppose, it
> is on the order of microseconds per write and the reply journal will
> eventually have to pay double for that anyway.
> 
> Also, somebody has to implement your NFS reply journal, further
> messing
> up knfsd.  I am having a hard time seeing what is good about a
> dedicated NFS reply journal.
> 
> Regards,
> 
> Daniel
> 

  reply	other threads:[~2006-05-08 18:22 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
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 [this message]
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=445F8C57.7000501@google.com \
    --to=phillips@google.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.