linux-kernel - Re: slow open() calls and o

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e7ca40f70706040659k20f4fac6n137a570080c84be5@mail.gmail.com>
Date:	Mon, 4 Jun 2007 09:59:19 -0400
From:	"Aaron Wiebe" <epiphani@...il.com>
To:	"Neil Brown" <neilb@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: slow open() calls and o_nonblock

On 6/3/07, Neil Brown <neilb@...e.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/