Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: chucklever@gmail.com
Cc: Krishna Kumar2 <krkumar2@in.ibm.com>,
	nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: Re: [NFS] NFS performance debugging
Date: Fri, 27 Jun 2008 14:12:36 -0400	[thread overview]
Message-ID: <1214590356.9235.1.camel@localhost> (raw)
In-Reply-To: <76bd70e30806270644j3e67c83and7b1f7fd6cc2f5f5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Fri, 2008-06-27 at 09:44 -0400, Chuck Lever wrote:

> >
> > (KK: for some reason, the real NFS mount gives all zero. Also, for
> > loopback, the read/write
> > BW is very poor: less than 40 Kb/s).
> 
> As an aside, Jim Rees pointed out to me that that should be KB/s, not
> Kb/s.  I will post a patch to address that.

Strictly speaking, neither of the above are correct: the SI abbreviation
for kilo is 'k'. IOW it should be 'kB/s'

Cheers
  Trond


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


  parent reply	other threads:[~2008-06-27 18:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 14:59 [NFS] NFS performance debuggins Adrian von Bidder
     [not found] ` <200806231659.58158-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-23 15:15   ` Trond Myklebust
2008-06-23 19:28   ` J. Bruce Fields
2008-06-24 10:17     ` [NFS] NFS performance debugging Adrian von Bidder
     [not found]       ` <200806241217.29243-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-24 20:29         ` J. Bruce Fields
2008-06-25  7:02           ` Adrian von Bidder
     [not found]             ` <200806250902.42880-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-25 13:20               ` Trond Myklebust
2008-06-25 13:59                 ` Steve Dickson
     [not found]                   ` <48624F34.1070108-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-06-27  7:30                     ` Krishna Kumar2
2008-06-27 13:44                       ` Chuck Lever
     [not found]                         ` <76bd70e30806270644j3e67c83and7b1f7fd6cc2f5f5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-27 18:12                           ` Trond Myklebust [this message]
2008-06-30  9:05                           ` Krishna Kumar2
2008-06-27 18:06                       ` Olga Kornievskaia
2008-06-25 16:56               ` J. Bruce Fields
2008-06-26  6:19                 ` Adrian von Bidder
     [not found]                   ` <200806260819.35108-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-26 17:03                     ` J. Bruce Fields
2008-06-27  6:24                       ` Adrian von Bidder
     [not found]                         ` <200806270824.54066-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-27 17:47                           ` J. Bruce Fields

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=1214590356.9235.1.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=SteveD@redhat.com \
    --cc=chucklever@gmail.com \
    --cc=krkumar2@in.ibm.com \
    --cc=nfs@lists.sourceforge.net \
    /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