From: Rodrigo S de Castro <rodsc@terra.com.br>
To: Nitin Gupta <nitingupta.mail@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: why its dead now?
Date: Mon, 14 Nov 2005 17:58:52 -0200 [thread overview]
Message-ID: <200511141758.52171.rodsc@terra.com.br> (raw)
In-Reply-To: <f68e01850511131035l3f0530aft6076f156d4f62171@mail.gmail.com>
Hi Nitin,
I didn't know you were working on a port of it to 2.6 version.
The project has been dead because I didn't have time to work on it after I
finished my Master's degree and also because nobody showed interest and had
enough time to port it to 2.6. Although it was not completely stable, it has
been used in many patchsets (ck, wolk) and I had really good feedbacks from
its users, in particular desktop users about smoother system degradations
when under memory pressure. It has never been officialy announced since there
is still a good deal of work to make it work with high memory systems, to
make it thread safe and probably some more testing and adjustments. With 2.6,
we still have rmap implementation that may help us improving the dynamic
adaptivity heuristic.
Answering your questions, from my experience developing the 2.4 version, it
doesn't seem to have any serious drawbacks, but it has not yet been
extensively tested to prove to be a valid idea (although our benchmarks show
to be) and it didn't reach an implementation level where it could be
considered to be possibly a configuration option, at least. I think it may be
really useful to port it to 2.6, for various reasons, such as:
- better change to prove this concept,
- it may turn out to be a good option for embedded systems,
- chance to improve the adaptivity heuristic (with rmap and maybe with other
2.6 mm updates, besides some ideas I have)
- with a thread safe, see how well it works with SMP systems.
I am interested in porting it to 2.6 and it's possible, although not yet sure,
that I get back to working on this project in the next weeks. Let's discuss
the status of your port and how we could work together to make it happen (we
could discuss further on the lc-devel list).
Best regards,
Rodrigo
On Sunday 13 November 2005 16:35, Nitin Gupta wrote:
> Hi,
> I've been working on 'compressed cache' feature
> (http://linuxcompressed.sourceforge.net/) for some time now. I'm
> basically porting it to 2.6 kernel series as it has already been
> developed for 2.4.x kernels.
> I'm wondering why this project is dead even when it showed great
> performance improvement when system is under memory pressure.
>
> Are there any serious drawbacks to this?
> Do you think it will be of any use if ported to 2.6 kernel?
>
> Your feedback will be really helpful.
>
> Thanks
>
> --
> 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-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-11-14 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 18:35 Nitin Gupta
2005-11-14 19:58 ` Rodrigo S de Castro [this message]
2005-11-15 3:28 ` Rik van Riel
2005-11-15 14:27 ` Scott F. H. Kaplan
2005-11-19 23:30 ` Rik van Riel
2005-11-20 2:24 ` Scott F. H. Kaplan
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=200511141758.52171.rodsc@terra.com.br \
--to=rodsc@terra.com.br \
--cc=linux-mm@kvack.org \
--cc=nitingupta.mail@gmail.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