From: Avi Kivity <avi@redhat.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.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, 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: Sun, 28 Jun 2009 10:42:57 +0300 [thread overview]
Message-ID: <4A471F01.7010400@redhat.com> (raw)
In-Reply-To: <63386a3d0906270618h5be01265v759f5acd1f49682f@mail.gmail.com>
On 06/27/2009 04:18 PM, Linus Walleij wrote:
> 2009/6/20 Dan Magenheimer<dan.magenheimer@oracle.com>:
>
>
>> We call this latter class "transcendent memory" and it
>> provides an interesting opportunity to more efficiently
>> utilize RAM in a virtualized environment. However this
>> "memory but not really memory" may also have applications
>> in NON-virtualized environments, such as hotplug-memory
>> deletion, SSDs, and page cache compression. Others have
>> suggested ideas such as allowing use of highmem memory
>> without a highmem kernel, or use of spare video memory.
>>
>
> Here is what I consider may be a use case from the embedded
> world: we have to save power as much as possible, so we need
> to shut off entire banks of memory.
>
> Currently people do things like put memory into self-refresh
> and then sleep, but for long lapses of time you would
> want to compress memory towards lower addresses and
> turn as many banks as possible off.
>
> So we have something like 4x16MB banks of RAM = 64MB RAM,
> and the most necessary stuff easily fits in one of them.
> If we can shut down 3x16MB we save 3 x power supply of the
> RAMs.
>
> However in embedded we don't have any swap, so we'd need
> some call that would attempt to remove a memory by paging
> out code and data that has been demand-paged in
> from the FS but no dirty pages, these should instead be
> moved down to memory which will be retained, and the
> call should fail if we didn't succeed to migrate all
> dirty pages.
>
> Would this be possible with transcendent memory?
>
You could do this with memory defragmentation, which is needed for
things like memory hotunplug ayway.
--
error compiling committee.c: too many arguments to function
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.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, 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: Sun, 28 Jun 2009 10:42:57 +0300 [thread overview]
Message-ID: <4A471F01.7010400@redhat.com> (raw)
In-Reply-To: <63386a3d0906270618h5be01265v759f5acd1f49682f@mail.gmail.com>
On 06/27/2009 04:18 PM, Linus Walleij wrote:
> 2009/6/20 Dan Magenheimer<dan.magenheimer@oracle.com>:
>
>
>> We call this latter class "transcendent memory" and it
>> provides an interesting opportunity to more efficiently
>> utilize RAM in a virtualized environment. However this
>> "memory but not really memory" may also have applications
>> in NON-virtualized environments, such as hotplug-memory
>> deletion, SSDs, and page cache compression. Others have
>> suggested ideas such as allowing use of highmem memory
>> without a highmem kernel, or use of spare video memory.
>>
>
> Here is what I consider may be a use case from the embedded
> world: we have to save power as much as possible, so we need
> to shut off entire banks of memory.
>
> Currently people do things like put memory into self-refresh
> and then sleep, but for long lapses of time you would
> want to compress memory towards lower addresses and
> turn as many banks as possible off.
>
> So we have something like 4x16MB banks of RAM = 64MB RAM,
> and the most necessary stuff easily fits in one of them.
> If we can shut down 3x16MB we save 3 x power supply of the
> RAMs.
>
> However in embedded we don't have any swap, so we'd need
> some call that would attempt to remove a memory by paging
> out code and data that has been demand-paged in
> from the FS but no dirty pages, these should instead be
> moved down to memory which will be retained, and the
> call should fail if we didn't succeed to migrate all
> dirty pages.
>
> Would this be possible with transcendent memory?
>
You could do this with memory defragmentation, which is needed for
things like memory hotunplug ayway.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-28 7:42 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 23:53 [RFC] transcendent memory for Linux Dan Magenheimer
2009-06-20 1:35 ` [RFC PATCH 0/4] transcendent memory ("tmem") " Dan Magenheimer
2009-06-20 1:35 ` Dan Magenheimer
2009-06-20 1:35 ` [RFC PATCH 1/4] tmem: infrastructure for tmem layer Dan Magenheimer
2009-06-20 1:35 ` Dan Magenheimer
2009-06-20 1:50 ` Rik van Riel
2009-06-20 1:50 ` Rik van Riel
2009-06-20 1:35 ` [RFC PATCH 2/4] tmem: precache implementation (layered on tmem) Dan Magenheimer
2009-06-20 1:35 ` Dan Magenheimer
2009-06-20 2:28 ` Rik van Riel
2009-06-20 2:28 ` Rik van Riel
2009-06-20 1:36 ` [RFC PATCH 3/4] tmem: preswap " Dan Magenheimer
2009-06-20 1:36 ` Dan Magenheimer
2009-06-20 1:36 ` [RFC PATCH 4/4] tmem: interface code for tmem on top of xen Dan Magenheimer
2009-06-20 1:36 ` Dan Magenheimer
2009-06-22 11:27 ` [RFC] transcendent memory for Linux Martin Schwidefsky
2009-06-22 11:27 ` Martin Schwidefsky
2009-06-22 20:41 ` Dan Magenheimer
2009-06-22 20:41 ` Dan Magenheimer
2009-06-22 14:31 ` Chris Friesen
2009-06-22 14:31 ` Chris Friesen
2009-06-22 20:50 ` Dan Magenheimer
2009-06-22 20:50 ` Dan Magenheimer
2009-06-24 15:04 ` Pavel Machek
2009-06-24 15:04 ` Pavel Machek
2009-06-29 14:34 ` Dan Magenheimer
2009-06-29 14:34 ` Dan Magenheimer
2009-06-29 20:36 ` Pavel Machek
2009-06-29 20:36 ` Pavel Machek
2009-06-29 21:13 ` Dan Magenheimer
2009-06-29 21:13 ` Dan Magenheimer
2009-06-29 21:23 ` Jeremy Fitzhardinge
2009-06-29 21:23 ` Jeremy Fitzhardinge
2009-06-29 21:57 ` Dan Magenheimer
2009-06-29 21:57 ` Dan Magenheimer
2009-06-29 22:15 ` Jeremy Fitzhardinge
2009-06-29 22:15 ` Jeremy Fitzhardinge
2009-06-30 21:21 ` Dan Magenheimer
2009-06-30 21:21 ` Dan Magenheimer
2009-06-30 22:46 ` Jeremy Fitzhardinge
2009-06-30 22:46 ` Jeremy Fitzhardinge
2009-07-01 23:02 ` Dan Magenheimer
2009-07-01 23:02 ` Dan Magenheimer
2009-07-01 23:31 ` Jeremy Fitzhardinge
2009-07-01 23:31 ` Jeremy Fitzhardinge
2009-07-02 6:38 ` Pavel Machek
2009-07-02 6:38 ` Pavel Machek
2009-07-02 14:03 ` Dan Magenheimer
2009-07-02 14:03 ` Dan Magenheimer
2009-06-27 13:18 ` Linus Walleij
2009-06-27 13:18 ` Linus Walleij
2009-06-28 7:42 ` Avi Kivity [this message]
2009-06-28 7:42 ` Avi Kivity
2009-06-29 14:44 ` Dan Magenheimer
2009-06-29 14:44 ` Dan Magenheimer
2009-07-01 3:41 ` Roland Dreier
2009-07-01 3:41 ` Roland Dreier
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=4A471F01.7010400@redhat.com \
--to=avi@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.