linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] VM kswapd autotuning vs. -ac7
Date: 07 Jun 2000 15:04:36 +0200	[thread overview]
Message-ID: <qwwhfb5prq3.fsf@sap.com> (raw)
In-Reply-To: Rik van Riel's message of "Wed, 7 Jun 2000 09:43:50 -0300 (BRST)"

Rik van Riel <riel@conectiva.com.br> writes:
> Ahh, but it could easily swap them out when the last of the
> pages is unmapped.
> 
> if (PageSHM(page) && not_in_use(page) && PageDirty(page)) {
> 	swapentry_t entry;
> 	entry.val = alloc_swap_entry();
> 	....
> 	rw_swap_page(page);
> }
> 
> And the next time it can be freed like a normal SwapCache
> page...

O.K. So what do I test in PageSHM()? Right now there is no such flag.

> > Thus shm does it's own page handling and swap out mechanism.
> > Since I do not know enough about the page cache I will not do
> > this before 2.5. If you think it can be easily done, feel free
> > to do it yourself or show me the way to go (But I will be on
> > vacation the next two weeks).
> 
> OK. The shrink_mmap() side of the story should be relatively
> easy (see above), but the ipc/shm.c part is a complete mystery
> to me ... ;(

You see and for me it's vice versa. The shm part is relatively
easy. Pages in shm do not get introduced into any other cache unless
they are swapped out. shm uses a very dumb algorithm to find swappable
pages when shm_swap is called.

If we want to introduce the shm pages into the lru lists, we need a
mark as shm page. Then we could perhaps make shm_swap obsolete and
leave the work to shrink_mmap. But shrink_mmap is new to me...

Greetings
		Christoph
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-06-07 13:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-01 22:31 Rik van Riel
2000-06-02 15:54 ` Christoph Rohland
2000-06-02 16:01   ` Rik van Riel
2000-06-03  9:02     ` Christoph Rohland
2000-06-03 20:47       ` Rik van Riel
2000-06-04 11:12         ` Christoph Rohland
2000-06-05  8:58           ` Christoph Rohland
2000-06-05 10:16             ` Rik van Riel
2000-06-07 10:23               ` Christoph Rohland
2000-06-07 12:43                 ` Rik van Riel
2000-06-07 13:04                   ` Christoph Rohland [this message]
2000-06-07 13:39                     ` Rik van Riel
2000-06-07 14:29                       ` Christoph Rohland
2000-06-07 14:43                         ` Stephen C. Tweedie
2000-06-08 15:04                           ` [PATCH,incomplete] shm integration into shrink_mmap Christoph Rohland
2000-06-08 15:21                             ` Juan J. Quintela
2000-06-08 15:35                             ` Rik van Riel
2000-06-07 13:32                 ` [PATCH] VM kswapd autotuning vs. -ac7 Stephen C. Tweedie
2000-06-07 14:09                   ` Jamie Lokier
2000-06-07 14:11                   ` Christoph Rohland
2000-06-07 14:17                     ` Stephen C. Tweedie

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=qwwhfb5prq3.fsf@sap.com \
    --to=cr@sap.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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