[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 9 Sep 2009 13:28:24 -0400 (EDT)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Jeff Layton <jlayton@...hat.com>
cc: linux-kernel@...r.kernel.org, samba@...ts.samba.org,
linux-cifs-client@...ts.samba.org
Subject: Re: 2.6.31-rc8: CIFS with 5 seconds hiccups
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists