mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS Performance on Linux 2.2.19 (RedHat version) -- lstat64() ?
Date: 05 Dec 2001 13:11:58 +0100	[thread overview]
Message-ID: <shsk7w1hnn5.fsf@charged.uio.no> (raw)
In-Reply-To: <OFEE87D44A.D1899606-ON85256B19.00026956@ma.lycos.com>
In-Reply-To: <OFEE87D44A.D1899606-ON85256B19.00026956@ma.lycos.com>

>>>>> " " == Joe Pranevich <Joe.Pranevich@corp.terralycos.com> writes:

     > but not in a precise testing environment. Where my confusion
     > comes in is that a simple "ls" against a directory with a
     > couple files takes approximately 4-5 times as long under Linux
     > as on Solaris. Doing a "strace -c" on the ls process shows that
     > nearly all of the time is being spent in lstat64(). (And yes, I
     > was using "ls --color=none" :) ) (Our application does a lot of
     > similar operations, so this is a valid test.)

Hi,

  Solaris is currently more efficient than we are when it comes to
filehandle and attribute caching, but together with Chuck Lever, we
worked hard over the summer to even the odds.

  My main suspect for your report is the NFSv3 operation
READDIRPLUS. Whereas ordinary NFSv2/v3 READDIR returns only the
filename + inode number for each directory entry, READDIRPLUS also
returns the NFS filehandle and full file attributes. With proper
caching, this is sufficient to save an entire LOOKUP RPC call per file
when you get to the stat() calls...

  I do have patches that you can test, though unfortunately only for
the 2.4. series. A backport to the 2.2.x series should be possible if
you're able and willing, but my own schedule unfortunately won't
permit it.
As far as I know, the 2.4 patches can be considered `production
quality' (meaning that I haven't seen any bugs reported over the last
couple of months), and I've been using them in production on our own
machines.

If you are interested, please first apply the attribute cache
improvements in

  http://www.fys.uio.no/~trondmy/src/2.4.16/linux-2.4.15-cto.dif

and then the readdirplus implementation in

  http://www.fys.uio.no/~trondmy/src/2.4.16/linux-2.4.15-rdplus.dif

Cheers,
   Trond

      reply	other threads:[~2001-12-05 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05  0:27 Joe.Pranevich
2001-12-05 12:11 ` Trond Myklebust [this message]

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=shsk7w1hnn5.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®