xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: James Harper <james.harper@bendigoit.com.au>, xen-devel@lists.xen.org
Subject: Re: tmem docs
Date: Tue, 28 May 2013 12:40:58 -0400	[thread overview]
Message-ID: <20130528164058.GB6073@phenom.dumpdata.com> (raw)
In-Reply-To: <27835fe7-1d80-4aea-8bca-4cb38dc42490@default>

On Tue, May 28, 2013 at 09:20:28AM -0700, Dan Magenheimer wrote:
> > From: Konrad Rzeszutek Wilk
> > Subject: Re: [Xen-devel] tmem docs
> > 
> > On Tue, May 28, 2013 at 12:26:15AM +0000, James Harper wrote:
> > > > On Mon, May 27, 2013 at 09:14:09AM +0000, James Harper wrote:
> > > > > Where is the best place to read about tmem hypercall abi? Should I start
> > > > > with the Linux implementation?
> > > >
> > > > I'm not really answering your question here.. but if you didn't see these links,
> > > > take a look, they might help:
> > > > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01892.html
> > >
> > > That all tells me about how great tmem is, and some of the interfaces exposed by Linux, but I can't
> > find anything about the interfaces exposed by Xen that Windows would need to use. It seems that the
> > interface is fairly thin though, and I have a few Windows related problems to solve first before I can
> > even think about making use of tmem.
> > 
> > Let's CC Dan here. He has a stash of documents on that.
> > 
> > But looking at the include/public/tmem.h it is very slim on comments. The ones
> > that are of interest to you (I think) are:
> > 
> > TMEM_DESTROY_POOL, TMEM_NEW_POOL, TMEM_PUT_PAGE, and TMEM_GET_PAGE.
> > 
> > > Thanks
> > > James
> 
> Hi James --
> 
> I'll be working for a few more weeks and would be happy
> to answer any questions I can.  However, I am no longer on the
> xen-devel email list so you will need to cc me directly.
> 
> I'm gathering you are trying to connect a Windows kernel to the
> Xen tmem ABI?  There have been various ideas proposed about
> connecting up Linux _userland_ apps to tmem and it may be possible
> to do that for Windows as well.  However, the existing ABI
> is probably best suited for a guest kernel, and I've never
> had access to Windows kernel source so I'm not in a position
> to judge how easy or how hard it would be to modify Windows
> kernel source to adapt it.  KY Srinivasan is currently working
> on cross-guest memory capacity optimization for Linux on HyperV
> and has expressed some interest in tmem for Windows so you
> may want to contact him to see if he's given it any thought.
> (kys@microsoft.com) KY was an early Xen contributor also.
> 
> The tmem ABI spec is here:
> 
> https://oss.oracle.com/projects/tmem/dist/documentation/api/tmemspec-v001.pdf 

Awesome.
> 
> As you can see by the date, that spec version is very old (2008)
> but, on quick scan, it is still 99% accurate.  The main difference
> I see is that (page 2, line 18) object identifiers are now
> 192-bit instead of 64-bit.  See reason for that change here:
> http://lists.xen.org/archives/html/xen-devel/2010-09/msg00069.html 
> 

Is there a source for the spec so I can modify it (And also
put the spec in the Xen codebase).

      reply	other threads:[~2013-05-28 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27  9:14 tmem docs James Harper
2013-05-27 11:14 ` Pasi Kärkkäinen
2013-05-28  0:26   ` James Harper
2013-05-28 14:49     ` Konrad Rzeszutek Wilk
2013-05-28 16:20       ` Dan Magenheimer
2013-05-28 16:40         ` Konrad Rzeszutek Wilk [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=20130528164058.GB6073@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xen.org \
    /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).