From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: linux-mm@kvack.org, kernel@tutu.ime.usp.br
Subject: Re: [RFC] Structure in Compressed Cache
Date: Tue, 31 Oct 2000 14:06:08 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010311404210.1475-100000@freak.distro.conectiva> (raw)
In-Reply-To: <20001030190922.A5183@linux.ime.usp.br>
On Mon, 30 Oct 2000, Rodrigo S. de Castro wrote:
> Hello,
>
> In my implementation of compressed cache (kernel 2.2.16), I
> started the project having my cache as a slab cache, structure
> provided by kernel. I have all step 1 (a cache with no compression)
> done, but I had a problem with marking pages in my cache. After an
> email sent to the list about this subject, I started looking at shared
> memory mechanism (mainly ipc/shm.c), and I saw that there's another
> way of making it: with a page table allocation and memory mapping. I
> could go on with my initial idea (with slab cache) but I think that
> doing the latter way (with page table and memory mapping) would be
> more complete (and, of course, harder). I will have a pool of
> (compressed) pages that gotta be always in memory and will be
> "between" physical memory and swap. As the project is growing I would
> like to define now which path to follow, taking in account
> completeness and upgradeability (to future versions of kernel). Which
> way do you think that is better? Please, I also ask you to tell me in
> case you know if there's another way, maybe better, of doing it.
Slab cache memory is physically contiguous and non swappable, so it may be
a waste to use it to cache userspace data.
--
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/
next prev parent reply other threads:[~2000-10-31 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 21:09 Rodrigo S. de Castro
2000-10-31 16:06 ` Marcelo Tosatti [this message]
2000-10-31 19:15 ` Rodrigo S. de Castro
2000-11-01 20:51 ` Rodrigo S. de Castro
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=Pine.LNX.4.21.0010311404210.1475-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=kernel@tutu.ime.usp.br \
--cc=linux-mm@kvack.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