linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Nitin Gupta" <nitingupta910@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Subject: Re: [RFC][PATCH 0/6] compcache: Compressed Caching
Date: Wed, 9 Apr 2008 10:32:06 +0530	[thread overview]
Message-ID: <4cefeab80804082202ub29fad6m2bb2337cbea6ed97@mail.gmail.com> (raw)
In-Reply-To: <20080408194740.1219e8b8.akpm@linux-foundation.org>

On Wed, Apr 9, 2008 at 8:17 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 21 Mar 2008 01:29:58 +0530 Nitin Gupta <nitingupta910@gmail.com> wrote:
>
>  > Subject: [RFC][PATCH 0/6] compcache: Compressed Caching
>
>  Didn't get many C's, did it?
>
>  Be sure to cc linux-kernel on the next version.
>
>

I have already posted it again on linux-kernel with link to
performance figures for allocator (TLSF vs SLUB):

see: http://lkml.org/lkml/2008/4/8/69


>  > Project home contains some performance numbers for TLSF and LZO.
>  > For general desktop use, this is giving *significant* performance gain
>  > under memory pressure. For now, it has been tested only on x86.
>
>  The values of "*significant*" should be exhaustively documented in the
>  patch changelogs. That is 100%-the-entire-whole-point of the patchset!
>  Omitting that information tends to reduce the number of C's.
>

I will also post performance numbers for compcache.
Desktop seems so much more responsive with this. I need to see how I
can quantify this.


>  Please feed all diffs through scripts/checkpatch.pl, contemplate the
>  result.
>
>  kmap_atomic() is (much) preferred over kmap().
>

We are doing compression and alloc (can sleep) between kmap/kunmap.
So, I used kmap() instead of kmap_atomic().



>  flush_dcache_page() is needed after the CPU modifies pagecache or anon page
>  by hand (generally linked to kmap[_atomic]()).
>

ok. I will add this.


>  The changelogs should include *complete* justification for the introduction
>  of a new allocator.  What problem is it solving, what are the possible
>  solutions to that problem, why this one was chosen, etc.  It's a fairly big
>  deal.
>

TLSF comparison with SLUB can be found here:

http://code.google.com/p/compcache/wiki/AllocatorsComparison


Thanks for review.

Regards,
Nitin

--
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>

  reply	other threads:[~2008-04-09  5:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 19:59 Nitin Gupta
2008-03-20 20:04 ` [RFC][PATCH 1/6] compcache: compressed RAM block device Nitin Gupta
2008-03-20 20:06 ` [RFC][PATCH 2/6] compcache: block device - internal defs Nitin Gupta
2008-03-20 20:08 ` [RFC][PATCH 3/6] compcache: TLSF Allocator interface Nitin Gupta
2008-03-20 20:10 ` [RFC][PATCH 4/6] compcache: TLSF Allocator Nitin Gupta
2008-03-20 20:11 ` [RFC][PATCH 5/6] compcache: TLSF Allocator - internal defs Nitin Gupta
2008-03-20 20:12 ` [RFC][PATCH 6/6] compcache: Documentation Nitin Gupta
2008-04-09  2:47 ` [RFC][PATCH 0/6] compcache: Compressed Caching Andrew Morton
2008-04-09  5:02   ` Nitin Gupta [this message]
2008-04-09  5:08     ` Andrew Morton

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=4cefeab80804082202ub29fad6m2bb2337cbea6ed97@mail.gmail.com \
    --to=nitingupta910@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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