linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Eckenfels <ecki-news2005-01@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux NFS vs NetApp
Date: Wed, 12 Jan 2005 00:36:40 +0100	[thread overview]
Message-ID: <E1CoVZ2-0006f7-00@calista.eckenfels.6bone.ka-ip.net> (raw)
In-Reply-To: <16868.19707.857446.864762@cse.unsw.edu.au>

In article <16868.19707.857446.864762@cse.unsw.edu.au> you wrote:
>> NetApp's WAFL only journals metadata in NVRAM ...
>> (one of the primary reasons its called WAFL is that the data-write only 
>> happens once..).

> That may be, though it doesn't fit with my (admittedly limitted)
> understanding of WAFL.

Yes, AFAIK the NVRAM is used for the RAID-4, independend of WAFL and  as a write-back cache. 

However since also the read performance of Linux NFS is bad (at least not
very well selftuning) the Hardware is not really the reason for the fast NFS
implementation.

Greetings
Bernd

  reply	other threads:[~2005-01-12  0:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <message from Phy Prabab on Monday January 10>
2005-01-11  2:54 ` Linux NFS vs NetApp Phy Prabab
2005-01-11  3:58   ` Anton Blanchard
2005-01-11  7:42     ` Joel Jaeggli
2005-01-11  9:19       ` Valdis.Kletnieks
2005-01-11 10:01         ` Jakob Oestergaard
2005-01-11 14:43           ` J. Bruce Fields
2005-01-12 11:32             ` Jakob Oestergaard
2005-01-11 18:55           ` Valdis.Kletnieks
2005-01-11  9:54   ` Neil Brown
2005-01-11 11:38     ` Lincoln Dale
2005-01-11 22:02       ` Neil Brown
2005-01-11 23:36         ` Bernd Eckenfels [this message]
2005-01-12  0:41           ` Trond Myklebust
     [not found] <200501111711.50218.as@cohaesio.com>
2005-01-11 16:21 ` J. Bruce Fields
2005-01-11 17:53   ` Anders Saaby

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=E1CoVZ2-0006f7-00@calista.eckenfels.6bone.ka-ip.net \
    --to=ecki-news2005-01@lina.inka.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).