All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "ospk-vm@lab.ntt.co.jp" <ospk-vm@lab.ntt.co.jp>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari
Date: Wed, 18 Mar 2009 18:11:34 +0900	[thread overview]
Message-ID: <49C0BAC6.7070103@lab.ntt.co.jp> (raw)
In-Reply-To: <49BFED6A.3050805@eu.citrix.com>

Stefano Stabellini wrote:
> Ian Jackson wrote:
> 
>> Stefano Stabellini writes ("Re: [Xen-devel] [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari"):
>>> I did a couple of quick tests and it seems that signals are faster then
>>> xenstore but still xenstore offers good performances.
>>>
>>> I measured the time using rdtsc at the sender size and at the receiver
>>> size, the difference between the two values is the following:
>>>
>>> signals:   368836
>>> xenstore: 1984632
>> This is with an unloaded xenstored, I take it.
> 
> 
> Yes

Thanks for measuring the numbers.  It made things clear.
I think we need a signal-based interface as Ian said previously.

On our test environment, AMD Barcelona 2.3GHz, the total cpu cycles of Kemari in 
userland when running I/O intensive applications is around 3000000.
Although Xen transferring code and QEMU saving code is processed concurrently, 
using xenstored for staring QEMU portion would lower the performance. 
Especially if the xenstored gets slower when items are loaded.

Yoshi

  reply	other threads:[~2009-03-18  9:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  5:47 [RFC][PATCH 00/13] Kemari: VM synchronization mechanism for fault tolerance Yoshiaki Tamura
2009-03-06  5:50 ` [RFC][PATCH 01/13] Kemari: add ECS_TAP state to event channel Yoshiaki Tamura
2009-03-06  5:53 ` [RFC][PATCH 02/13] Kemari: core kemari code Yoshiaki Tamura
2009-03-06  5:54 ` [RFC][PATCH 03/13] Kemari: change parameter type of xc_{set, get}_hvm_param Yoshiaki Tamura
2009-03-06  5:56 ` [RFC][PATCH 04/13] Kemari: Kemari controller interface in libxc Yoshiaki Tamura
2009-03-06  6:26 ` [RFC][PATCH 05/13] Kemari: Kemari sender Yoshiaki Tamura
2009-03-06  6:46 ` [RFC][PATCH 06/13] Kemari: Kemari receiver Yoshiaki Tamura
2009-03-06  6:46 ` [RFC][PATCH 07/13] Kemari: add Kemari support to python Yoshiaki Tamura
2009-03-06  6:46 ` [RFC][PATCH 08/13] Kemari: add dev state "Attached" " Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 09/13] Kemari: add XenbusStateAttached to xenbus Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 10/13] Kemari: XenbusStateAttached handler for blkback Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 11/13] Kemari: XenbusStateAttached handler for netback Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari Yoshiaki Tamura
2009-03-06 11:39   ` Stefano Stabellini
2009-03-06 16:20     ` Yoshiaki Tamura
2009-03-17 17:55       ` Stefano Stabellini
2009-03-17 18:21         ` Ian Jackson
2009-03-17 18:35           ` Stefano Stabellini
2009-03-18  9:11             ` Yoshiaki Tamura [this message]
2009-03-18  9:34               ` Keir Fraser
2009-03-18 12:45                 ` Yoshiaki Tamura
2009-03-18 12:46               ` Stefano Stabellini
2009-03-18 13:06                 ` Keir Fraser
2009-03-19  5:54                   ` Yoshiaki Tamura
2009-03-18 17:37               ` Christopher Head
2009-03-19  6:07                 ` Yoshiaki Tamura
2009-03-16 18:05     ` Ian Jackson
2009-03-06  6:47 ` [RFC][PATCH 13/13] Kemari: use shared region with to flip logdirty_bitmap Yoshiaki Tamura
  -- strict thread matches above, loose matches on Subject: below --
2009-03-12  1:22 [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari Yoshiaki Tamura
2009-03-24  6:59 ` Yoshiaki Tamura

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=49C0BAC6.7070103@lab.ntt.co.jp \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=ospk-vm@lab.ntt.co.jp \
    --cc=stefano.stabellini@eu.citrix.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.