From: Andrew Morton <akpm@zip.com.au>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Jannik Rasmussen <jannik@east.no>, linux-kernel@vger.kernel.org
Subject: Re: Error 3c900 driver in 2.2.19?
Date: Tue, 28 Aug 2001 11:19:53 -0700 [thread overview]
Message-ID: <3B8BE0C9.78B12BB@zip.com.au> (raw)
In-Reply-To: <3B8BD508.47CCA66D@zip.com.au> <Pine.LNX.4.30.0108281935230.2909-100000@mustard.heime.net>
Roy Sigurd Karlsbakk wrote:
>
> > Networking needs to allocate memory at interrupt time. This is
> > referred to as "atomic allocation". The only way in which this
> > can be successful is for the VM system to ensure that there is
> > a pool of immediately-allocatable memory lying around.
> >
> > The 2.2 kernel uses the tunables in /proc/sys/vm/freepages to
> > decide how large that pool should be. Machines which sustain
> > a high network load commonly require more memory than the
> > default freepages setting provides. People who encounter network
> > Rx allocation failures with 2.2 kernels do report that increasing
> > the freepages tunables fixes the problem.
> >
> > -
> >
>
> Thanks
>
> But... Should the server hang after experiencing problems with this? On
> 2.2.19?
>
Absolutely not. If the network driver experiences 32 successive
memory allocation failures it will fall back to a timer-driven mode
where it tries to refill its buffer ring once per second. This
code works.
If your machine is completely locking up and needs a reset then
something is presumably not handling out-of-memory correctly.
What do you mean by "the server hangs"?
-
next prev parent reply other threads:[~2001-08-28 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B8BD0F8.7308F0C9@zip.com.au>
2001-08-28 17:21 ` Error 3c900 driver in 2.2.19? Roy Sigurd Karlsbakk
2001-08-28 17:29 ` Andrew Morton
2001-08-28 17:36 ` Roy Sigurd Karlsbakk
2001-08-28 18:19 ` Andrew Morton [this message]
2001-08-28 19:42 ` Roy Sigurd Karlsbakk
[not found] <3B8AD082.DB477F80@zip.com.au>
2001-08-28 12:23 ` Roy Sigurd Karlsbakk
2001-08-27 13:27 Roy Sigurd Karlsbakk
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=3B8BE0C9.78B12BB@zip.com.au \
--to=akpm@zip.com.au \
--cc=jannik@east.no \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.