From: Jeff Layton <jlayton@redhat.com>
To: Christoph Lameter <cl@linux-foundation.org>
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
Date: Wed, 9 Sep 2009 14:02:57 -0400 [thread overview]
Message-ID: <20090909140257.35ede0cc@tlielax.poochiereds.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0909091327370.32067@V090114053VZO-1>
On Wed, 9 Sep 2009 13:28:24 -0400 (EDT)
Christoph Lameter <cl@linux-foundation.org> 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 <jlayton@redhat.com>
next prev parent reply other threads:[~2009-09-09 18:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:27 Christoph Lameter
2009-09-05 11:10 ` Jeff Layton
2009-09-09 16:33 ` Christoph Lameter
2009-09-09 16:53 ` Jeff Layton
2009-09-09 17:07 ` Christoph Lameter
2009-09-09 17:20 ` Jeff Layton
2009-09-09 17:28 ` Christoph Lameter
2009-09-09 18:02 ` Jeff Layton [this message]
2009-09-09 21:27 ` Christoph Lameter
2009-09-10 0:55 ` Jeff Layton
2009-09-10 18:53 ` Christoph Lameter
2009-09-10 19:33 ` Jeff Layton
2009-09-10 19:42 ` Christoph Lameter
2009-09-10 20:57 ` Jeff Layton
2009-09-10 21:27 ` Christoph Lameter
2009-09-11 0:19 ` Jeff Layton
2009-09-14 20:10 ` Christoph Lameter
2009-09-15 22:34 ` Jeff Layton
2009-09-16 16:26 ` Christoph Lameter
2009-09-18 14:24 ` Jeff Layton
2009-09-14 20:16 ` (64 bit dump) " Christoph Lameter
2009-09-10 21:42 ` Christoph Lameter
2009-09-09 17:33 ` Christoph Lameter
2009-09-09 17:57 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090909140257.35ede0cc@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=cl@linux-foundation.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®