From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: A scrub daemon (prezeroing)
Date: Wed, 2 Feb 2005 21:00:46 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61L.0502022000470.9448@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <20050202153256.GA19615@logos.cnet>
On Wed, 2 Feb 2005, Marcelo Tosatti wrote:
> > Some architectures tend to have spare DMA engines lying around. There's
> > no need to use the CPU for zeroing pages. How feasible would it be for
> > scrubd to use these?
[...]
> I suppose you are talking about DMA engines which are not being driven
> by any driver ?
E.g. the Broadcom's MIPS64-based SOCs have four general purpose DMA
engines onchip which can transfer data to/from the memory controller in
32-byte chunks over the 256-bit internal bus. We have hardly any use for
these devices and certainly not for all four of them.
> Sounds very interesting idea to me. Guess it depends on whether the cost of
> DMA write for memory zeroing, which is memory architecture/DMA engine dependant,
> offsets the cost of CPU zeroing.
I suppose so, at least with the Broadcom's chips you avoid cache
trashing, yet you don't need to care about stale data as coherency between
CPUs and the onchip memory controller is maintained automatically by
hardware.
Maciej
--
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>
next prev parent reply other threads:[~2005-02-02 21:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 20:29 Christoph Lameter
2005-01-27 12:15 ` David Woodhouse
2005-01-27 13:12 ` Robin Holt
2005-01-27 13:14 ` David Woodhouse
2005-01-27 17:02 ` Christoph Lameter
2005-02-08 11:31 ` Ralf Baechle
2005-02-02 15:32 ` Marcelo Tosatti
2005-02-02 19:05 ` Christoph Lameter
2005-02-02 16:31 ` Marcelo Tosatti
2005-02-02 21:31 ` Christoph Lameter
2005-02-02 21:39 ` David Woodhouse
2005-02-03 3:06 ` Rik van Riel
2005-02-03 23:39 ` Paul Mackerras
2005-02-04 0:59 ` Christoph Lameter
2005-02-04 5:30 ` Paul Mackerras
2005-02-04 6:26 ` Christoph Lameter
2005-02-04 6:43 ` Nick Piggin
2005-02-04 6:50 ` Christoph Lameter
2005-02-04 9:20 ` Paul Mackerras
2005-02-04 9:28 ` Andi Kleen
2005-02-04 17:02 ` Christoph Lameter
2005-02-04 22:25 ` Paul Mackerras
2005-02-02 21:00 ` Maciej W. Rozycki [this message]
2005-02-02 21:33 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 23:13 Prezeroing V3 [1/4]: Allow request for zeroed memory Christoph Lameter
2005-01-08 21:12 ` Hugh Dickins
2005-01-08 21:56 ` David S. Miller
2005-01-21 20:15 ` A scrub daemon (prezeroing) 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=Pine.LNX.4.61L.0502022000470.9448@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.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