From: "Pedro M. Rodrigues" <pmanuel@myrealbox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: nfs & "Warning - running *really* short on DMA buffers"
Date: Fri, 30 Aug 2002 13:42:40 +0200 [thread overview]
Message-ID: <3D6F7650.32578.A1B755@localhost> (raw)
In-Reply-To: <1030705134.3180.9.camel@irongate.swansea.linux.org.uk>
I do wan't to tune the vm settings, these warnings may not be
fatal but it's not pretty to have hundreds of those in the console
and log files. Bear with me on this one, but i remember doing exactly
that in the past, tuning /proc/sys/vm/freepages. How does one
acomplish that nowadays? I looked at the kernel source documentation
and still found references to freepages, but vm/freepages doesn't
exist anymore. Kernel is 2.4.18-10 from Redhat.
Regards,
Pedro
On 30 Aug 2002 at 11:58, Alan Cox wrote:
> On Fri, 2002-08-30 at 08:02, Pedro M. Rodrigues wrote:
> > Hello to all! While preparing to migrate some servers to Redhat
> > 7.3 and doing some nfs tests before deployment i came across this
> > "Warning - running *really* short on DMA buffers" error message
> > repeated several times in dmesg and /var/log/messages. Something
> > like this:
>
> They are warnings not fatal, at most they slowed you down due to lack
> of resources. You might want to tune the vm settings to keep more
> pages reserved for atomic allocation
>
>
next prev parent reply other threads:[~2002-08-30 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 7:02 PROBLEM: nfs & "Warning - running *really* short on DMA buffers" Pedro M. Rodrigues
2002-08-30 10:58 ` Alan Cox
2002-08-30 11:42 ` Pedro M. Rodrigues [this message]
2002-08-30 12:18 ` Rik van Riel
2002-08-31 13:29 ` Pedro M. Rodrigues
2002-08-31 17:22 ` Pedro M. Rodrigues
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=3D6F7650.32578.A1B755@localhost \
--to=pmanuel@myrealbox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).