mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Art Haas" <ahaas@airmail.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel memory requirements and BK [SOLVED]
Date: Mon, 8 Nov 2004 19:52:47 -0600	[thread overview]
Message-ID: <20041109015247.GB2701@artsapartment.org> (raw)
In-Reply-To: <200411070004_MC3-1-8E11-3F5E@compuserve.com>

On Sun, Nov 07, 2004 at 12:02:07AM -0500, Chuck Ebbert wrote:
> Art Haas wrote:
> 
> > With the 2.6.9 and 2.6.10-rc kernels, BK bombs out with
> > out-of-memory errors once the repository checking begins.
> 
> There's nothing wrong with BK's performance that can't be
> solved by a terahertz processor and a terabyte of RAM. ;)
> 
> But these patches might help:
> 

[ snip first patch added into Linus's BK tree]

> ============================================================================
> # spurious_oomkill.patch
> #
> #       Prevent spurious out of memory process kills.
> #       Reported to work by testers on lkml.
> #
> #       Patch by Rik van Riel <riel@redhat.com>
> #       Status: NOT in 2.6.10
> #
> --- 2.6.9/mm/vmscan.c
> +++ 2.6.9.1/mm/vmscan.c
> @@ -379,7 +379,7 @@
>  
>                 referenced = page_referenced(page, 1);
>                 /* In active use or really unfreeable?  Activate it. */
> -               if (referenced && page_mapping_inuse(page))
> +               if (referenced && sc->priority && page_mapping_inuse(page))
>                         goto activate_locked;
>  
>  #ifdef CONFIG_SWAP
> @@ -715,7 +715,7 @@
>                 if (page_mapped(page)) {
>                         if (!reclaim_mapped ||
>                             (total_swap_pages == 0 && PageAnon(page)) ||
> -                           page_referenced(page, 0)) {
> +                           (page_referenced(page, 0) && sc->priority)) {
>                                 list_add(&page->lru, &l_active);
>                                 continue;
>                         }

This patch did the trick for me. I booted up my 2.6.8.1 kernel, did a
'bk pull' to get the code (Sunday Morning), and added in this patch. After
building and installing the patched kernel, I did another 'bk pull'
later and things worked fine. Consider me one more person to vouch for
this patch solving the OOM problem!

Art Haas
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

      reply	other threads:[~2004-11-09  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-07  5:02 Kernel memory requirements and BK Chuck Ebbert
2004-11-09  1:52 ` Art Haas [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=20041109015247.GB2701@artsapartment.org \
    --to=ahaas@airmail.net \
    --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

all inboxes | Powered by JetHome®