From: "Rodrigo S. de Castro" <rcastro@linux.ime.usp.br>
To: linux-mm@kvack.org
Subject: [RFC] Structure in Compressed Cache
Date: Mon, 30 Oct 2000 19:09:22 -0200 [thread overview]
Message-ID: <20001030190922.A5183@linux.ime.usp.br> (raw)
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.
Thank you in advance,
--
Rodrigo S. de Castro <rcastro@linux.ime.usp.br>
University of Sao Paulo - Brazil
Compressed caching - http://tutu.ime.usp.br
--
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 reply other threads:[~2000-10-30 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 21:09 Rodrigo S. de Castro [this message]
2000-10-31 16:06 ` [RFC] Structure in Compressed Cache Marcelo Tosatti
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=20001030190922.A5183@linux.ime.usp.br \
--to=rcastro@linux.ime.usp.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 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.