All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: nfsv4@linux-nfs.org, linux-nfs@vger.kernel.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [PATCH 0/3] Fix the Linux rpc-over-tcp server performance
Date: Wed, 12 Aug 2009 10:20:41 -0400	[thread overview]
Message-ID: <20090812142041.GA12753@fieldses.org> (raw)
In-Reply-To: <x49ab25w4ja.fsf@segfault.boston.devel.redhat.com>

On Wed, Aug 12, 2009 at 09:22:17AM -0400, Jeff Moyer wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes:
> 
> > On Mon, May 18, 2009 at 05:47:56PM -0400, Trond Myklebust wrote:
> >> I squashed the previous set of 4 incremental patches into 3. Otherwise
> >> there should be no differences w.r.t. the set that Jeff tested.
> >
> > Apologies for the long delay.... Unfortunately, I can't reproduce any of
> > this at all: I reliably get about 112MB/s regardless of what combination
> > of these patches I apply (including none).  This is over gigabit
> > ethernet to a server exporting a filesystem on raid 0 over 3 sata disks
> > which iozone locally reports getting just over 200MB/s reads from.
> >
> > Any suggestions?
> 
> Well, you gave me nothing to go on here, Bruce!

Apologies for the lack of details....

> I assume you're using
> the deadline I/O scheduler on the NFS server, is that right?  If not,
> you should be.

Oops, sorry, no. Looks like it doesn't allow setting a scheduler on md0,
so I'm assuming I should be setting it on the component drives.

> Second, are you using iozone to reproduce?
> 
>   iozone -s 2000000 -r 64 -f /mnt/test/testfile -i 1 -w

Yes, I was using your commandline.

> That's the command line I was using.  Third, I reproduced this on
> 2.6.30-rc1.  Perhaps you should start there and make sure you at least
> see the same problem on that kernel.  Otherwise, maybe we've made up for
> the performance elsewhere.

Right, could be, I was working on top of 2.6.31-rc1.

> Finally, didn't you revert the autotuning patch?  If so, you wouldn't
> see this problem.  Let me know how this goes, and if you still can't
> reproduce it I'll setup for testing it here.

Right, I re-applied the autotuning patch before applying the others.

Thanks for the suggestions.

--b.
_______________________________________________
NFSv4 mailing list
NFSv4@linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

  reply	other threads:[~2009-08-12 14:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 21:47 [PATCH 0/3] Fix the Linux rpc-over-tcp server performance Trond Myklebust
     [not found] ` <20090518214756.786.28129.stgit-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-18 21:47   ` [PATCH 3/3] SUNRPC: Fix svc_tcp_recvfrom() Trond Myklebust
2010-03-18 21:21     ` J. Bruce Fields
2010-04-02 21:00       ` J. Bruce Fields
2009-05-18 21:47   ` [PATCH 1/3] SUNRPC: Fix the TCP server's send buffer accounting Trond Myklebust
     [not found]     ` <20090518214756.786.58191.stgit-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-19  3:06       ` J. Bruce Fields
2009-05-18 21:47   ` [PATCH 2/3] SUNRPC: Fix the TCP write space reservations for deferred requests Trond Myklebust
     [not found]     ` <20090518214756.786.33956.stgit-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-19 22:23       ` J. Bruce Fields
2009-06-20 21:44         ` Trond Myklebust
     [not found]           ` <1245534248.5182.45.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-08-24 21:32             ` J. Bruce Fields
2009-05-19 15:14   ` [PATCH 0/3] Fix the Linux rpc-over-tcp server performance Jeff Moyer
2009-08-12  2:43 ` J. Bruce Fields
2009-08-12 13:22   ` Jeff Moyer
2009-08-12 14:20     ` J. Bruce Fields [this message]
2009-08-12 17:02       ` Jeff Moyer
2009-08-12 22:32         ` J. Bruce Fields
2009-08-12 22:40           ` Trond Myklebust
2009-08-13 13:05           ` Jeff Moyer

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=20090812142041.GA12753@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@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.