All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: clameter@sgi.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, dgc@sgi.com,
	Eric Dumazet <dada1@cosmosbay.com>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [RFC 2/3] SLUB: Implement targeted reclaim and partial list defragmentation
Date: 05 May 2007 12:38:25 +0200	[thread overview]
Message-ID: <p738xc3wo66.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070504221708.596112123@sgi.com>

clameter@sgi.com writes:
> 
> NOTE: This patch is for conceptual review. I'd appreciate any feedback
> especially on the locking approach taken here. It will be critical to
> resolve the locking issue for this approach to become feasable.

Do you have any numbers on how this improves dcache reclaim under memory pressure?

-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: clameter@sgi.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, dgc@sgi.com,
	Eric Dumazet <dada1@cosmosbay.com>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [RFC 2/3] SLUB: Implement targeted reclaim and partial list defragmentation
Date: 05 May 2007 12:38:25 +0200	[thread overview]
Message-ID: <p738xc3wo66.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070504221708.596112123@sgi.com>

clameter@sgi.com writes:
> 
> NOTE: This patch is for conceptual review. I'd appreciate any feedback
> especially on the locking approach taken here. It will be critical to
> resolve the locking issue for this approach to become feasable.

Do you have any numbers on how this improves dcache reclaim under memory pressure?

-Andi

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

  parent reply	other threads:[~2007-05-05  9:40 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 22:15 [RFC 0/3] Slab Defrag / Slab Targeted Reclaim and general Slab API changes clameter
2007-05-04 22:15 ` clameter
2007-05-04 22:15 ` [RFC 1/3] SLUB: slab_ops instead of constructors / destructors clameter
2007-05-04 22:15   ` clameter
2007-05-05 10:14   ` Pekka Enberg
2007-05-05 10:14     ` Pekka Enberg
2007-05-05 15:43     ` Christoph Lameter
2007-05-05 15:43       ` Christoph Lameter
2007-05-06 19:19   ` Bert Wesarg
2007-05-06 19:19     ` Bert Wesarg
2007-05-06 19:46     ` Satyam Sharma
2007-05-06 19:46       ` Satyam Sharma
2007-05-04 22:15 ` [RFC 2/3] SLUB: Implement targeted reclaim and partial list defragmentation clameter
2007-05-04 22:15   ` clameter
2007-05-04 23:03   ` Christoph Lameter
2007-05-04 23:03     ` Christoph Lameter
2007-05-05  1:04     ` Randy Dunlap
2007-05-05  1:04       ` Randy Dunlap
2007-05-05  1:07       ` Christoph Lameter
2007-05-05  1:07         ` Christoph Lameter
2007-05-05  5:32   ` William Lee Irwin III
2007-05-05  5:32     ` William Lee Irwin III
2007-05-05 15:35     ` Christoph Lameter
2007-05-05 15:35       ` Christoph Lameter
2007-05-05 10:38   ` Andi Kleen [this message]
2007-05-05 10:38     ` Andi Kleen
2007-05-05 15:42     ` Christoph Lameter
2007-05-05 15:42       ` Christoph Lameter
2007-05-05 17:11       ` Andi Kleen
2007-05-05 17:11         ` Andi Kleen
2007-05-09 15:05   ` Mel Gorman
2007-05-09 15:05     ` Mel Gorman
2007-05-09 16:34     ` Christoph Lameter
2007-05-09 16:34       ` Christoph Lameter
2007-05-04 22:15 ` [RFC 3/3] Support targeted reclaim and slab defrag for dentry cache clameter
2007-05-04 22:15   ` clameter
2007-05-05  5:07 ` [RFC 0/3] Slab Defrag / Slab Targeted Reclaim and general Slab API changes Eric Dumazet
2007-05-05  5:07   ` Eric Dumazet
2007-05-05  5:14   ` Christoph Lameter
2007-05-05  5:14     ` Christoph Lameter
2007-05-05  5:41     ` Eric Dumazet
2007-05-05  5:41       ` Eric Dumazet
2007-05-05  7:37       ` Eric Dumazet
2007-05-05  7:37         ` Eric Dumazet
2007-05-05 15:39       ` Christoph Lameter
2007-05-05 15:39         ` Christoph Lameter

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=p738xc3wo66.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=clameter@sgi.com \
    --cc=dada1@cosmosbay.com \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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.