mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	NeilBrown <neilb@suse.de>, Adrian Bunk <bunk@stusta.de>
Subject: Re: [bisect] NFS regression breaks X
Date: Wed, 09 May 2007 18:17:44 -0400	[thread overview]
Message-ID: <1178749064.6760.14.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0705091440461.4062@woody.linux-foundation.org>

On Wed, 2007-05-09 at 14:51 -0700, Linus Torvalds wrote:
> 
> On Wed, 9 May 2007, Jeff Garzik wrote:
> > 
> > I love bisect :)
> 
> Yeah, me too.
> 
> > bisect has identified the following commit as the one that
> > causes my GNOME login to die, within 10 seconds of logging in:
> > 
> > 	commit 2bea90d43a050bbc4021d44e59beb34f384438db
> 
> Ok, that commit looks nice in many ways, so I'd be loathe to revert it 
> entirely.
> 
> Can you try it with this patch that re-introduces the "total overkill" 
> slack calculations, and probably makes them even worse (there's a few 
> left-shifts added, and now it will left-shift the extra slacktoo).
> 
> But there are also some unexplained changes in that patch, so maybe the 
> size allocation isn't the big problem. For example, now "call_allocate()" 
> will set task->tk_status to zero which is totally strange.
> 
> But if it's the allocation that is too small, this patch may help.
> 
> Trond, Chuck?

We'd really like to fix this by getting the pre-allocation tables right
in nfs4xdr.c. Chuck has already identified one incorrect value:

http://linux-nfs.org/cgi-bin/gitweb.cgi?p=nfs-2.6.git;a=commitdiff;h=6ce7dc940701cf3fde3c6e826a696b333092cbb1;hp=aa3d1faebe6e214cd96be0e587571477ff6fd9fc

that I just asked you to pull as part of a series of bugfixes. I'm
hoping that will suffice to fix Jeff's case too.

Trond

  reply	other threads:[~2007-05-09 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 21:30 Jeff Garzik
2007-05-09 21:51 ` Linus Torvalds
2007-05-09 22:17   ` Trond Myklebust [this message]
2007-05-09 22:48   ` Jeff Garzik
2007-05-09 22:03 ` Trond Myklebust
2007-05-09 22:52   ` Andrew Morton
2007-05-10  0:10     ` Trond Myklebust
2007-05-10 13:36       ` Chuck Lever
2007-05-11 22:54       ` Jeff Garzik

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=1178749064.6760.14.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=chuck.lever@oracle.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=torvalds@linux-foundation.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®