From: Al Boldi <a1426z@gawab.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Massive slowdown when re-querying large nfs dir
Date: Sun, 4 Nov 2007 19:03:12 +0300 [thread overview]
Message-ID: <200711041903.12976.a1426z@gawab.com> (raw)
In-Reply-To: <20071104133642.GS15111@parisc-linux.org>
Matthew Wilcox wrote:
> How about tcpdumping and seeing what requests are flowing across the
> wire? You might be able to figure out what's being done differently.
I think lookup is faster than getattr.
Thanks!
--
Al
next prev parent reply other threads:[~2007-11-04 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 4:58 Massive slowdown when re-querying large nfs dir Al Boldi
2007-11-04 13:36 ` Matthew Wilcox
2007-11-04 16:03 ` Al Boldi [this message]
2007-11-06 11:28 ` Al Boldi
2007-11-07 6:19 ` Andrew Morton
2007-11-07 7:28 ` Neil Brown
2007-11-07 9:36 ` Al Boldi
2007-11-07 17:05 ` Andrew Morton
2007-11-08 7:44 ` Al Boldi
2007-11-08 9:04 ` Andrew Morton
2007-11-07 21:58 ` Neil Brown
2007-11-07 22:01 ` Massive slowdown when re-querying large nfs dir - CORRECTION Neil Brown
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=200711041903.12976.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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).