All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: "Avi Kivity" <avi@redhat.com>,
	"Christian Bornträger" <borntraeger@de.ibm.com>,
	kvm@vger.kernel.org,
	"Christian Ehrhardt" <ehrhardt@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts.
Date: Wed, 20 May 2009 12:28:38 +0930	[thread overview]
Message-ID: <200905201228.38718.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A12E37C.700@cs.ualberta.ca>

On Wed, 20 May 2009 02:21:08 am Cam Macdonell wrote:
> Avi Kivity wrote:
> > Christian Bornträger wrote:
> >>> To summarize, Anthony thinks it should use virtio, while I believe
> >>> virtio is useful for exporting guest memory, not for importing host
> >>> memory.

Yes, precisely.

But what's it *for*, this shared memory?  Implementing shared memory is 
trivial.  Using it is harder.  For example, inter-guest networking: you'd have 
to copy packets in and out, making it slow as well as losing abstraction.

The only interesting idea I can think of is exposing it to userspace, and 
having that run some protocol across it for fast app <-> app comms.  But if 
that's your plan, you still have a lot of code the write!

So I guess I'm missing the big picture here?

Thanks,
Rusty.


  reply	other threads:[~2009-05-20  2:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 16:26 [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts Cam Macdonell
2009-05-18 14:07 ` Christian Borntraeger
2009-05-18 14:26   ` Avi Kivity
2009-05-19  9:00     ` Christian Bornträger
2009-05-19  9:10       ` Avi Kivity
2009-05-19 16:51         ` Cam Macdonell
2009-05-20  2:58           ` Rusty Russell [this message]
2009-05-20  7:33             ` Christian Bornträger
2009-05-20  8:45               ` Avi Kivity
2009-05-20  9:07                 ` Christian Bornträger
2009-05-20  9:11                   ` Avi Kivity
2009-05-20  9:20                     ` Christian Bornträger
2009-05-25  6:18               ` Rusty Russell
2009-05-20  8:07             ` François Diakhate
2009-05-19 18:39       ` Anthony Liguori
2009-05-20  7:33         ` Christian Bornträger
2009-05-20 13:26           ` Anthony Liguori
2009-05-18 16:56   ` Cam Macdonell

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=200905201228.38718.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cam@cs.ualberta.ca \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.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 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.