Linux NFS development
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Aioanei Rares <krnl.list@gmail.com>,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: 2.6.29.1: Pid: 2831, comm: nfsd Not tainted 2.6.29.1 #4
Date: Wed, 22 Apr 2009 18:51:21 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0904221850360.17988@p34.internal.lan> (raw)
In-Reply-To: <4807377b0904221541j7e2c4c0bh50d76d494b3cb306@mail.gmail.com>



On Wed, 22 Apr 2009, Jesse Brandeburg wrote:

> On Tue, Apr 21, 2009 at 1:00 PM, Aioanei Rares <krnl.list@gmail.com> wrote:
>> Justin Piszcz wrote:
>>> This has been happening with 2.6.28.(x) and now 2.6.29.(x), can anyone
>>> suggest the possible root cause of this problem, re: the nfsd page
>>> allocation
>>> failures:
>
>> Yes, it happened to me too on a Debian unstable machine with more than one
>> kernel, starting with 2.6.28 until now. I have a feeling it's a
>> Debian-specific problem rather than a kernel one.
>
> you may both want to try
> echo 16384 > /proc/sys/vm/min_free_kbytes
>
> or some other value depending on your amount of ram.  This change will
> increase the minimum amount of memory available for network memory
> allocations, which are called from softirq context to refill the NIC's
> receive buffers.
>

Will give it a shot, the default was already pretty close to the 
suggestion, 11441, if it recurs, will increase further.

Thanks,

Justin.

      reply	other threads:[~2009-04-22 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:09 2.6.29.1: Pid: 2831, comm: nfsd Not tainted 2.6.29.1 #4 Justin Piszcz
2009-04-21 20:00 ` Aioanei Rares
2009-04-22 22:41   ` Jesse Brandeburg
2009-04-22 22:51     ` Justin Piszcz [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=alpine.DEB.2.00.0904221850360.17988@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=krnl.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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