linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harshula Jayasuriya <harshula@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>, Judith Flo Gaya <jflo@imppc.org>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: problem with nfs latency during high IO
Date: Thu, 17 Mar 2011 12:21:24 +1100	[thread overview]
Message-ID: <1300324884.7042.4.camel@serendib> (raw)
In-Reply-To: <7D458ECC-9AFB-4791-94EF-736061BD1095@oracle.com>

Hi Chuck & Judith,

On Tue, 2011-03-15 at 14:15 -0400, Chuck Lever wrote:
> On Mar 15, 2011, at 2:03 PM, Chuck Lever wrote:
> > On Mar 15, 2011, at 1:25 PM, Judith Flo Gaya wrote:

> >> BTW i understand the time issue, but again, if the version of the
> kernel that the red hat has installed allows me to get the information
> soon, why a newer kernel in fedora does not?
> > 
> > Sounds like a bug.  Fedora kernels newer than 2.6.32 should work as
> well as, or better than, RHEL 6.
> 
> Looks like commit acdc53b2 "NFS: Replace __nfs_write_mapping with
> sync_inode()" removes the code that holds i_mutex while trying to
> flush writes before a GETATTR.  This means application writes can
> possibly starve a stat(2) call.  Trond, this seems like a
> regression...?

RHEL 6.0 released with RH kernel 2.6.32-71 and it *does* contain the
commit acdc53b2 "NFS: Replace __nfs_write_mapping with sync_inode()"
backported to 2.6.32. So, I doubt that the reported bad Fedora
performance is due to that commit.

cya,
#


  reply	other threads:[~2011-03-17  1:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 12:58 problem with nfs latency during high IO Judith Flo Gaya
2011-03-15 16:24 ` Chuck Lever
2011-03-15 17:25   ` Judith Flo Gaya
2011-03-15 18:03     ` Chuck Lever
2011-03-15 18:15       ` Chuck Lever
2011-03-17  1:21         ` Harshula Jayasuriya [this message]
2011-03-15 21:33       ` Judith Flo Gaya
2011-03-15 21:28         ` Chuck Lever
2011-03-15 21:58           ` Judith Flo Gaya
2011-03-15 22:10             ` Chuck Lever
2011-03-16 11:45               ` Judith Flo Gaya
2011-03-16 13:24                 ` Chuck Lever
2011-03-16 13:42                   ` peter.staubach
2011-03-16 15:18                   ` Jim Rees
2011-03-16 15:31                     ` Jim Rees
2011-03-16 16:52                       ` Judith Flo Gaya
2011-03-16 23:51                 ` Simon Kirby
  -- strict thread matches above, loose matches on Subject: below --
2011-03-15 16:25 Judith Flo Gaya

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=1300324884.7042.4.camel@serendib \
    --to=harshula@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=jflo@imppc.org \
    --cc=linux-nfs@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).