All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lse-tech@lists.sourceforge.net
Subject: Re: [PATCH] Move cache_reap out of timer context
Date: Sat, 17 Jul 2004 20:52:56 +0200	[thread overview]
Message-ID: <20040717185256.GA5815@elte.hu> (raw)
In-Reply-To: <20040714180942.GA18425@sgi.com>


* Dimitri Sivanich <sivanich@sgi.com> wrote:

> I'm submitting two patches associated with moving cache_reap
> functionality out of timer context.  Note that these patches do not
> make any further optimizations to cache_reap at this time.
> 
> The first patch adds a function similiar to schedule_delayed_work to
> allow work to be scheduled on another cpu.
> 
> The second patch makes use of schedule_delayed_work_on to schedule
> cache_reap to run from keventd.
> 
> These patches apply to 2.6.8-rc1.
> 
> Signed-off-by: Dimitri Sivanich <sivanich@sgi.com>

looks good to me and i agree with moving this unbound execution-time
function out of irq context. I suspect this should see some -mm testing
first/too?

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lse-tech@lists.sourceforge.net
Subject: Re: [PATCH] Move cache_reap out of timer context
Date: Sat, 17 Jul 2004 20:52:56 +0200	[thread overview]
Message-ID: <20040717185256.GA5815@elte.hu> (raw)
In-Reply-To: <20040714180942.GA18425@sgi.com>

* Dimitri Sivanich <sivanich@sgi.com> wrote:

> I'm submitting two patches associated with moving cache_reap
> functionality out of timer context.  Note that these patches do not
> make any further optimizations to cache_reap at this time.
> 
> The first patch adds a function similiar to schedule_delayed_work to
> allow work to be scheduled on another cpu.
> 
> The second patch makes use of schedule_delayed_work_on to schedule
> cache_reap to run from keventd.
> 
> These patches apply to 2.6.8-rc1.
> 
> Signed-off-by: Dimitri Sivanich <sivanich@sgi.com>

looks good to me and i agree with moving this unbound execution-time
function out of irq context. I suspect this should see some -mm testing
first/too?

	Ingo
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-07-17 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 18:09 [PATCH] Move cache_reap out of timer context Dimitri Sivanich
2004-07-14 18:09 ` Dimitri Sivanich
2004-07-17 18:52 ` Ingo Molnar [this message]
2004-07-17 18:52   ` Ingo Molnar
2004-07-19 14:42   ` Dimitri Sivanich
2004-07-19 14:42     ` Dimitri Sivanich
2004-07-28  7:03 ` Andrew Morton
2004-07-28  7:03   ` 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=20040717185256.GA5815@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=manfred@colorfullife.com \
    --cc=sivanich@sgi.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 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.