public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rudy Zijlstra <rudy@edsons.demon.nl>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	nfs <nfs@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] Kernel BUG
Date: Sat, 23 Dec 2006 00:46:30 +0100	[thread overview]
Message-ID: <458C6E56.3070700@edsons.demon.nl> (raw)
In-Reply-To: <1166794920.32117.42.camel@twins>

Peter Zijlstra wrote:

>On Fri, 2006-12-22 at 12:59 +0100, Rudy Zijlstra wrote:
>  
>
>>Hi,
>>
>>I have a system where whenever i trigger a ongoing consistent NFS load i 
>>get the following kernel BUG:
>>
>>----------
>>kernel BUG at mm/truncate.c:311!
>>    
>>
>
>Lotsa changes there:
>try these:
> http://client.linux-nfs.org/Linux-2.6.x/2.6.19/linux-2.6.19-NFS_ALL.dif
>
>And:
>  http://lkml.org/lkml/2006/12/19/279
>
>  
>
Thanks, i have now a 2.6.19.1 patched with the above NFS_ALL patchset 
running under load since about 17:00 and still going strong. So seems to 
have solved the problem!

Also, performance seems to have significantly increased. I am testing 
this with MythTv with the storage over NFS. With HD LiveTV (which  is 
what i use to test this), this translates into about 43Mbps total load, 
from almost 15Mbps video stream which is present 3x on the ethernet:
1/ from card to NFS disk
2/ read from NFS disk
3/ stream to viewer app.

Doing this with HD streams before the patch set resulted in regular 
picture hickups. No hickups visible anymore (that i have seen, i have 
not been present all this time).

Regards,

Rudy

      reply	other threads:[~2006-12-22 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2006-12-22 23:46   ` Rudy Zijlstra [this message]

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=458C6E56.3070700@edsons.demon.nl \
    --to=rudy@edsons.demon.nl \
    --cc=Trond.Myklebust@netapp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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