qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v5 4/5] Inter-VM shared memory PCI device
Date: Tue, 11 May 2010 12:05:14 -0500	[thread overview]
Message-ID: <4BE98E4A.3010708@codemonkey.ws> (raw)
In-Reply-To: <AANLkTimE5RgJukRA1UtioN8NJ4RUpl3OHa1dsskGqi7h@mail.gmail.com>

On 05/11/2010 11:39 AM, Cam Macdonell wrote:
>
> Most of the people I hear from who are using my patch are using a peer
> model to share data between applications (simulations, JVMs, etc).
> But guest-to-host applications work as well of course.
>
> I think "transparent migration" can be achieved by making the
> connected/disconnected state transparent to the application.
>
> When using the shared memory server, the server has to be setup anyway
> on the new host and copying the memory region could be part of that as
> well if the application needs the contents preserved.  I don't think
> it has to be handled by the savevm/loadvm operations.  There's little
> difference between naming one VM the master or letting the shared
> memory server act like a master.
>    

Except that to make it work with the shared memory server, you need the 
server to participate in the live migration protocol which is something 
I'd prefer to avoid at it introduces additional down time.

Regards,

Anthony Liguori

> I think abstractions on top of shared memory could handle
> disconnection issues (sort of how TCP handles them for networks) if
> the application needs it.  Again, my opinion is to leave it to the
> application to decide what it necessary.
>
> Cam
>    

  reply	other threads:[~2010-05-11 18:18 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 17:53 [Qemu-devel] [PATCH v5 0/5] PCI Shared Memory device Cam Macdonell
2010-04-21 17:53 ` [Qemu-devel] [PATCH v5 1/5] Device specification for shared memory PCI device Cam Macdonell
2010-04-21 17:53   ` [Qemu-devel] [PATCH v5 2/5] Support adding a file to qemu's ram allocation Cam Macdonell
2010-04-21 17:53     ` [Qemu-devel] [PATCH v5 3/5] Add functions for assigning ioeventfd and irqfds Cam Macdonell
2010-04-21 17:53       ` [Qemu-devel] [PATCH v5 4/5] Inter-VM shared memory PCI device Cam Macdonell
2010-04-21 18:00         ` [Qemu-devel] [PATCH v5 5/5] shared memory server for inter-VM shared memory Cam Macdonell
2010-05-05 16:57         ` [Qemu-devel] [PATCH v5 4/5] RESEND: Inter-VM shared memory PCI device Cam Macdonell
2010-05-06 17:32         ` [Qemu-devel] Re: [PATCH v5 4/5] " Anthony Liguori
2010-05-06 17:59           ` Cam Macdonell
2010-05-10 11:59         ` Avi Kivity
2010-05-10 15:22           ` Cam Macdonell
2010-05-10 15:28             ` Avi Kivity
2010-05-10 15:38               ` Anthony Liguori
2010-05-10 16:20                 ` Cam Macdonell
2010-05-10 16:52                   ` Anthony Liguori
2010-05-18 16:58                     ` Cam Macdonell
2010-05-18 17:27                       ` Avi Kivity
2010-05-10 16:59                 ` Avi Kivity
2010-05-10 17:25                   ` Anthony Liguori
2010-05-10 17:43                     ` Cam Macdonell
2010-05-10 17:52                       ` Anthony Liguori
2010-05-10 18:01                         ` Cam Macdonell
2010-05-11  7:59                         ` Avi Kivity
2010-05-11 13:10                           ` Anthony Liguori
2010-05-11 14:03                             ` Avi Kivity
2010-05-11 14:17                               ` Cam Macdonell
2010-05-11 14:53                                 ` Avi Kivity
2010-05-11 15:51                                   ` Anthony Liguori
2010-05-11 16:39                                     ` Cam Macdonell
2010-05-11 17:05                                       ` Anthony Liguori [this message]
2010-05-11 17:50                                         ` Cam Macdonell
2010-05-11 18:13                                         ` Avi Kivity
2010-05-12 15:32                                           ` Cam Macdonell
2010-05-12 15:48                                             ` Avi Kivity
2010-05-11 18:09                                     ` Avi Kivity
2010-05-11  7:55                     ` Avi Kivity
2010-05-10 15:41               ` Cam Macdonell
2010-05-10 16:40                 ` Avi Kivity
2010-05-10 16:48                   ` Cam Macdonell
2010-05-12 15:49                     ` Avi Kivity
2010-05-12 16:14                       ` Cam Macdonell
2010-05-12 16:45                         ` Avi Kivity
2010-05-10 23:17           ` Cam Macdonell
2010-05-11  8:03             ` Avi Kivity
2010-05-13 21:10           ` Cam Macdonell
2010-05-15  6:05             ` Avi Kivity
2010-05-10 10:43       ` [Qemu-devel] Re: [PATCH v5 3/5] Add functions for assigning ioeventfd and irqfds Avi Kivity
2010-05-10 15:13         ` Cam Macdonell
2010-05-10 15:17           ` Avi Kivity
2010-05-10 10:39     ` [Qemu-devel] Re: [PATCH v5 2/5] Support adding a file to qemu's ram allocation Avi Kivity
2010-05-10 15:32       ` 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=4BE98E4A.3010708@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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).