From: Rik van Riel <riel@redhat.com>
To: Nitin Gupta <nitingupta.mail@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: why its dead now?
Date: Mon, 14 Nov 2005 22:28:46 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.63.0511142227540.15035@cuia.boston.redhat.com> (raw)
In-Reply-To: <f68e01850511131035l3f0530aft6076f156d4f62171@mail.gmail.com>
On Mon, 14 Nov 2005, Nitin Gupta wrote:
> Are there any serious drawbacks to this?
Compressed caching may be hard to tune right for some workloads.
I cannot see any other drawbacks - certainly nothing that should
keep you from working on it...
> Do you think it will be of any use if ported to 2.6 kernel?
It has the potential to be very useful.
--
All Rights Reversed
--
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-15 3:28 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
2005-11-15 3:28 ` Rik van Riel [this message]
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=Pine.LNX.4.63.0511142227540.15035@cuia.boston.redhat.com \
--to=riel@redhat.com \
--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