Date: Wed, 9 Sep 2009 13:28:24 -0400 (EDT)
From: Christoph Lameter <cl@linux-foundation.org>
To: Jeff Layton <jlayton@redhat.com>
cc: linux-kernel@vger.kernel.org, samba@lists.samba.org,
       linux-cifs-client@lists.samba.org
Subject: Re: 2.6.31-rc8: CIFS with 5 seconds hiccups
In-Reply-To: <20090909132039.1ca47cd4@tlielax.poochiereds.net>
Message-ID: <alpine.DEB.1.10.0909091327370.32067@V090114053VZO-1>
References: <alpine.DEB.1.10.0909041217520.7209@V090114053VZO-1> <20090905071052.50501826@tlielax.poochiereds.net> <alpine.DEB.1.10.0909091009120.28070@V090114053VZO-1> <20090909125352.1c7b57d2@tlielax.poochiereds.net> <alpine.DEB.1.10.0909091304001.32067@V090114053VZO-1>
 <20090909132039.1ca47cd4@tlielax.poochiereds.net>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 905
Lines: 22

On Wed, 9 Sep 2009, Jeff Layton wrote:

> That'll stop your client from requesting oplocks, but that won't
> prevent others from doing so. If my suspicion is correct, then another
> client is holding an oplock and the server needs to break it before it
> can reply to yours.
>
> Unfortunately I doubt there's much you can do from your client to
> prevent that (if that is the case). There may be a way to turn off
> oplocks on the server side, but that may very well be even worse for
> performance.

Hmmm... We can look at that.

Another interesting tidbit is that I have never seen this from a 64 bit
Linux kernel. Only occurs with 32 bit kernels it seems.

--
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/