From: "Aaron Wiebe" <epiphani@gmail.com>
To: "Neil Brown" <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: slow open() calls and o_nonblock
Date: Mon, 4 Jun 2007 09:59:19 -0400 [thread overview]
Message-ID: <e7ca40f70706040659k20f4fac6n137a570080c84be5@mail.gmail.com> (raw)
In-Reply-To: <18019.26871.317501.633363@notabene.brown>
On 6/3/07, Neil Brown <neilb@suse.de> wrote:
>
> Have you tried the "nocto" mount option for your NFS filesystems.
>
> The cache-coherency rules of NFS require the client to check with the
> server at each open. If you are the sole client on this filesystem,
> then you don't need the same cache-coherency, and "nocto" will tell
> the NFS client not to both checking with the server in information is
> available in cache.
No I haven't - I will research this a little further today. While
we're not the only client using these filesystems, this process is
(currently) the only process that writes to these files. Thanks for
the suggestion.
-Aaron
next prev parent reply other threads:[~2007-06-04 13:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 18:52 slow open() calls and o_nonblock Aaron Wiebe
2007-06-03 19:16 ` Davide Libenzi
2007-06-03 23:56 ` John Stoffel
2007-06-04 1:05 ` Aaron Wiebe
2007-06-04 1:20 ` Neil Brown
2007-06-04 13:59 ` Aaron Wiebe [this message]
2007-06-04 1:25 ` Bernd Eckenfels
2007-06-04 0:27 ` David Schwartz
2007-06-04 1:05 ` Al Viro
2007-06-04 1:19 ` Bernd Eckenfels
2007-06-04 13:49 ` Alan Cox
2007-06-04 14:04 ` Aaron Wiebe
2007-06-04 14:17 ` John Stoffel
2007-06-04 14:24 ` Aaron Wiebe
2007-06-04 14:20 ` Aaron Wiebe
2007-06-04 15:42 ` Trond Myklebust
2007-06-04 15:59 ` Aaron Wiebe
2007-06-04 16:26 ` Aaron Wiebe
2007-06-04 19:46 ` Trond Myklebust
2007-06-04 20:32 ` David Schwartz
2007-06-04 14:39 ` Aaron Wiebe
-- strict thread matches above, loose matches on Subject: below --
2007-06-04 3:57 Albert Cahalan
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=e7ca40f70706040659k20f4fac6n137a570080c84be5@mail.gmail.com \
--to=epiphani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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.