Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753914AbZIISDs (ORCPT ); Wed, 9 Sep 2009 14:03:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753279AbZIISDr (ORCPT ); Wed, 9 Sep 2009 14:03:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54598 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752483AbZIISDr (ORCPT ); Wed, 9 Sep 2009 14:03:47 -0400 Date: Wed, 9 Sep 2009 14:02:57 -0400 From: Jeff Layton To: Christoph Lameter 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 Message-ID: <20090909140257.35ede0cc@tlielax.poochiereds.net> In-Reply-To: References: <20090905071052.50501826@tlielax.poochiereds.net> <20090909125352.1c7b57d2@tlielax.poochiereds.net> <20090909132039.1ca47cd4@tlielax.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1321 Lines: 33 On Wed, 9 Sep 2009 13:28:24 -0400 (EDT) Christoph Lameter wrote: > 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. > That sounds rather strange. Maybe we do have a bug of some sort? The thing to do might be to get a binary capture of the 32-bit traffic around the time of the stalls. We could then inspect the packets and see whether we have something wrong in there. -- Jeff Layton -- 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/