From: Le Rouzic <aime.le-rouzic@bull.net>
To: nfsv4-request@linux-nfs.org
Cc: linux-nfs@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Results of a Robustness Regression tests and Performances campaign on linux-2.6.25-rc6-CITI_NFS4_ALL-1
Date: Fri, 06 Jun 2008 11:15:55 +0200 [thread overview]
Message-ID: <4849004B.2010406@bull.net> (raw)
Hi,
The results of a Robustness Regression tests and Performances campaign
on linux-2.6.25-rc6 plus
the linux-2.6.25-rc6-CITI_NFS4_ALL-1 path are available at :
http://nfsv4.bullopensource.org/
Those results include kerberos flavors krb5, krb5i, krb5p on Intel
x86_64 machines.
I needed also to add a patch found at http://lkml.org/lkml/2008/2/29/443
to fix an the infinite loop in generic_file_splice_read() we can see
with nfsv4 when nfsd looping.
Best regards
--
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name : Aime Le Rouzic
Mail : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail : aime.le-rouzic@bull.net
Phone : 33 (4) 76.29.75.51
Fax : 33 (4) 76.29.75.18
-----------------------------------------------------------------
reply other threads:[~2008-06-06 9:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4849004B.2010406@bull.net \
--to=aime.le-rouzic@bull.net \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4-request@linux-nfs.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.