linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Ingo Molnar <mingo@chiara.csoma.elte.hu>,
	Rik van Riel <riel@nl.linux.org>,
	Christoph Rohland <hans-christoph.rohland@sap.com>,
	MM mailing list <linux-mm@kvack.org>,
	woodman@missioncriticallinux.com,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [Patch] shm cleanups
Date: 05 Nov 1999 13:35:36 +0100	[thread overview]
Message-ID: <qwwpuxp9kvb.fsf@sap.com> (raw)
In-Reply-To: Andrea Arcangeli's message of "05 Nov 1999 01:14:04 +0100"

Andrea Arcangeli <andrea@suse.de> writes:

> Ingo Molnar <mingo@chiara.csoma.elte.hu> writes:
> 
> > [Christoph, are you still seeing the same kind of bad swapping behavior
> > with pre1-2.3.26?]
> 
> If you still get process killed during heavy swapout (cause OOM of
> an ATOMIC allocation) please try to increase the ATOMIC pool before
> designing a separate pool. We just have a pool for atomic allocation
> it may not be large enough for the increased pressure on the regular pages.
> 
>         echo 1000 2000 4000 >/proc/sys/vm/freepages
> 
> This way you'll basically waste 16mbyte of ram.  It's just to check if
> the ATOMIC allocation shortage is the source of the segfault or not.

O.k. with and without these settings 2.3.26-pre2 looks pretty good
about allocating bounce buffers and swapping highmem pages.

To swap shm the first part of the following patch is definitely
needed. The second part makes the machine probably much more useable
if we have problems allocating bounce buffers. Which now hardly ever
happens when stresstesting my 8GB machine.

Linus, could you please apply this?

        Christoph

--- 2.3.25/ipc/shm.c    Tue Nov  2 12:46:29 1999
+++ make25/ipc/shm.c    Thu Nov  4 12:47:14 1999
@@ -788,10 +789,10 @@
                unlock_kernel();
                return 0;
        }
-       if (page_count(page_map))
+       if (page_count(page_map) != 1)
                goto check_table;
        if (!(page_map = prepare_highmem_swapout(page_map)))
-               goto check_table;
+               goto failed;
        shp->shm_pages[idx] = swp_entry_to_pte(swap_entry);
        swap_successes++;
        shm_swp++;
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  reply	other threads:[~1999-11-05 12:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-03 21:30 Christoph Rohland
1999-11-04  8:10 ` Ingo Molnar
1999-11-04 12:40   ` Christoph Rohland
1999-11-04 17:58     ` Ingo Molnar
1999-11-04 19:02       ` Rik van Riel
1999-11-04 22:30         ` Ingo Molnar
1999-11-05  0:14           ` Andrea Arcangeli
1999-11-05 12:35             ` Christoph Rohland [this message]
1999-11-05 13:18               ` Andrea Arcangeli
1999-11-05 16:16                 ` Christoph Rohland
1999-11-05 16:21                   ` Andrea Arcangeli
1999-11-05 16:28                     ` Christoph Rohland
1999-11-05 10:36           ` Christoph Rohland
  -- strict thread matches above, loose matches on Subject: below --
1999-11-03 19:17 Christoph Rohland

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=qwwpuxp9kvb.fsf@sap.com \
    --to=hans-christoph.rohland@sap.com \
    --cc=andrea@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --cc=riel@nl.linux.org \
    --cc=torvalds@transmeta.com \
    --cc=woodman@missioncriticallinux.com \
    /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