From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: 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>
Subject: RE: [RFC] transcendent memory for Linux
Date: Mon, 29 Jun 2009 14:13:56 -0700 (PDT) [thread overview]
Message-ID: <6639b922-4ed7-48fd-9a3d-c78a4f93355c@default> (raw)
In-Reply-To: <20090629203619.GA6611@elf.ucw.cz>
> > It is documented currently at:
> >
> > http://oss.oracle.com/projects/tmem/documentation/api/
> >
> > (just noticed I still haven't posted version 0.0.2 which
> > has a few minor changes).
> >
> > I will add a briefer description of this API in Documentation/
>
> Please do.
OK, will do.
> At least TMEM_NEW_POOL() looks quite ugly. Why uuid? Mixing flags into
> size argument is strange.
The uuid is only used for shared pools. If two different
"tmem clients" (guests) agree on a 128-bit "shared secret",
they can share a tmem pool. For ocfs2, the 128-bit uuid in
the on-disk superblock is used for this purpose to implement
shared precache. (Pages evicted by one cluster node
can be used by another cluster node that co-resides on
the same physical system.)
The (page)size argument is always fixed (at PAGE_SIZE) for
any given kernel. The underlying implementation can
be capable of supporting multiple pagesizes.
So for the basic precache and preswap uses, "new pool"
has a very simple interface.
> > It is in-kernel only because some of the operations have
> > a parameter that is a physical page frame number.
>
> In-kernel API is probably better described as function prototypes.
Good idea. I will do that.
Thanks,
Dan
--
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>
next prev parent reply other threads:[~2009-06-29 21:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 23:53 Dan Magenheimer
2009-06-20 1:35 ` [RFC PATCH 0/4] transcendent memory ("tmem") " Dan Magenheimer
2009-06-20 1:35 ` [RFC PATCH 1/4] tmem: infrastructure for tmem layer Dan Magenheimer
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 2:28 ` Rik van Riel
2009-06-20 1:36 ` [RFC PATCH 3/4] tmem: preswap " Dan Magenheimer
2009-06-20 1:36 ` [RFC PATCH 4/4] tmem: interface code for tmem on top of xen Dan Magenheimer
2009-06-22 11:27 ` [RFC] transcendent memory for Linux Martin Schwidefsky
2009-06-22 20:41 ` Dan Magenheimer
2009-06-22 14:31 ` Chris Friesen
2009-06-22 20:50 ` Dan Magenheimer
2009-06-24 15:04 ` Pavel Machek
2009-06-29 14:34 ` Dan Magenheimer
2009-06-29 20:36 ` Pavel Machek
2009-06-29 21:13 ` Dan Magenheimer [this message]
2009-06-29 21:23 ` Jeremy Fitzhardinge
2009-06-29 21:57 ` Dan Magenheimer
2009-06-29 22:15 ` Jeremy Fitzhardinge
2009-06-30 21:21 ` Dan Magenheimer
2009-06-30 22:46 ` Jeremy Fitzhardinge
2009-07-01 23:02 ` Dan Magenheimer
2009-07-01 23:31 ` Jeremy Fitzhardinge
2009-07-02 6:38 ` Pavel Machek
2009-07-02 14:03 ` Dan Magenheimer
2009-06-27 13:18 ` Linus Walleij
2009-06-28 7:42 ` Avi Kivity
2009-06-29 14:44 ` Dan Magenheimer
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=6639b922-4ed7-48fd-9a3d-c78a4f93355c@default \
--to=dan.magenheimer@oracle.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=dave.mccracken@oracle.com \
--cc=jeremy@goop.org \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtosatti@redhat.com \
--cc=npiggin@suse.de \
--cc=pavel@ucw.cz \
--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