Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752401AbXFDBV3 (ORCPT ); Sun, 3 Jun 2007 21:21:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750759AbXFDBVX (ORCPT ); Sun, 3 Jun 2007 21:21:23 -0400 Received: from ns1.suse.de ([195.135.220.2]:46879 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750750AbXFDBVW (ORCPT ); Sun, 3 Jun 2007 21:21:22 -0400 From: Neil Brown To: "Aaron Wiebe" Date: Mon, 4 Jun 2007 11:20:55 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18019.26871.317501.633363@notabene.brown> Cc: linux-kernel@vger.kernel.org, "John Stoffel" Subject: Re: slow open() calls and o_nonblock In-Reply-To: message from Aaron Wiebe on Sunday June 3 References: <18019.21781.470399.393340@stoffel.org> X-Mailer: VM 7.19 under Emacs 21.4.1 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D > You can certainly open the file, but not block on the call to do it. > What confuses me is why the kernel would "block" for 415ms on an open > call. Thats an eternity to suspend a process that has to distribute > data such as this. 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. This should speed up the time for open considerably. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/