All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Florin Iucha <florin@iucha.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20-rc1: CIFS cheers, NFS4 jeers
Date: Tue, 27 Feb 2007 21:36:23 -0500	[thread overview]
Message-ID: <45E4EAA7.2090007@tmr.com> (raw)
In-Reply-To: <20070226064500.GZ29073@iucha.net>

Florin Iucha wrote:
> Hello, it's me and my 70 GB of photos again.
> 
> I have tested both CIFS and NFSv4 clients in kernel 2.6.20-rc1 . CIFS
> passed with flying colors and NFSv4 stalled after 7 GB.
> 
> Configuration:
> 
>    Server: PIII/1GHz, 512 MB RAM, Debian testing,
>       distro kernel 2.6.18-3-vserver-686, Intel E1000 NIC, 
>       filesystem 170 GB ext3 with default mkfs values on a SATA disk
>       
>    Client: AMD x2 4200+, 2 GB RAM, Debian testing/unstable
>       kernel 2.6.20-rc1, Marvell SKGE onboard,
>       filesystem 120 GB ext3 with default mkfs values on a SATA disk
> 
Neil has been diddling NFS, I did some light testing with 2.6.20-git14 
with 190GB of mp3 and mpg files (library of congress folk music) without 
hangs. Just "did it work" tests, copy 20-30GB to server, do md5 on the 
data pulled back from the server.

Didn't hang, performance testing later.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2007-02-28  2:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26  6:45 2.6.20-rc1: CIFS cheers, NFS4 jeers Florin Iucha
2007-02-26  6:48 ` Correction 2.6.21-rc1 Was: " Florin Iucha
2007-02-28  2:36 ` Bill Davidsen [this message]
2007-02-28  4:03   ` 2.6.21-rc1: " Florin Iucha
2007-02-28 13:35     ` Bill Davidsen
2007-03-01  5:52 ` 2.6.20-rc1: " Andrew Morton
2007-03-02  3:02   ` Florin Iucha
2007-03-02 14:39     ` Florin Iucha

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=45E4EAA7.2090007@tmr.com \
    --to=davidsen@tmr.com \
    --cc=florin@iucha.net \
    --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 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.