All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Juan J. Quintela" <quintela@fi.udc.es>
To: Christoph Rohland <cr@sap.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH,incomplete] shm integration into shrink_mmap
Date: 08 Jun 2000 17:21:30 +0200	[thread overview]
Message-ID: <yttpupsb3lx.fsf@serpe.mitica> (raw)
In-Reply-To: Christoph Rohland's message of "08 Jun 2000 17:04:24 +0200"

>>>>> "christoph" == Christoph Rohland <cr@sap.com> writes:

Hi christoph

christoph> Here is my first proposal for changing shm to be integrated into
christoph> shrink_mmap.

christoph> It gives you a function 'int shm_write_swap (struct page *page)' to
christoph> write out a page to swap and replace the pte in the shm structures.  I
christoph> tested the stuff with no swapping and it seems stable so far. But
christoph> shm_write_swap is completely untested.

christoph> It probably needs to add the pages in shm_nopage_core to your lru
christoph> queues and of course it needs the calls from shrink_mmap.

christoph> I think it would be nicer to only have a notify function instead of
christoph> shm_write_swap, which gets the page and the swap_entry and can simply
christoph> put the swap_entry into the shm structures without handling the
christoph> swapping at all.

christoph> What do you think?
christoph>         		Christoph

It lacks the cleanup of the SHM page bit :)))
But it looks great so far.  I am working just now it the shrink_mmap
integration.

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy
--
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-08 15:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-01 22:31 [PATCH] VM kswapd autotuning vs. -ac7 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
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 [this message]
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=yttpupsb3lx.fsf@serpe.mitica \
    --to=quintela@fi.udc.es \
    --cc=cr@sap.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    --cc=sct@redhat.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 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.