From: Roland Dreier <rdreier@cisco.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
npiggin@suse.de, chris.mason@oracle.com, kurt.hackel@oracle.com,
dave.mccracken@oracle.com, Avi Kivity <avi@redhat.com>,
jeremy@goop.org, Rik van Riel <riel@redhat.com>,
alan@lxorguk.ukuu.org.uk, Rusty Russell <rusty@rustcorp.com.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
akpm@osdl.org, Marcelo Tosatti <mtosatti@redhat.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
tmem-devel@oss.oracle.com, sunil.mushran@oracle.com,
linux-mm@kvack.org, Himanshu Raj <rhim@microsoft.com>,
linux-embedded@vger.kernel.org
Subject: Re: [RFC] transcendent memory for Linux
Date: Tue, 30 Jun 2009 20:41:01 -0700 [thread overview]
Message-ID: <aday6r9gjea.fsf@cisco.com> (raw)
In-Reply-To: <5331ec14-c599-4317-bd5b-55911b8ee916@default> (Dan Magenheimer's message of "Mon, 29 Jun 2009 07:44:50 -0700 (PDT)")
> One issue though: I would guess that copying pages of memory
> could be very slow in an inexpensive embedded processor.
And copying memory could very easily burn enough power by keeping the
CPU busy that you lose the incremental gain of turning the memory off
vs. just going to self refresh. (And the copying latency would easily
be as bad as the transition latency to/from self-refresh).
- R.
prev parent reply other threads:[~2009-07-01 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cd40cd91-66e9-469d-b079-3a899a3ccadb@default>
2009-06-27 13:18 ` [RFC] transcendent memory for Linux Linus Walleij
2009-06-28 7:42 ` Avi Kivity
2009-06-29 14:44 ` Dan Magenheimer
2009-07-01 3:41 ` Roland Dreier [this message]
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=aday6r9gjea.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=avi@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=jeremy@goop.org \
--cc=kurt.hackel@oracle.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtosatti@redhat.com \
--cc=npiggin@suse.de \
--cc=rhim@microsoft.com \
--cc=riel@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=sunil.mushran@oracle.com \
--cc=tmem-devel@oss.oracle.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).