From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gal Hammer <ghammer@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio: improve virtio devices initialization time
Date: Fri, 12 Jan 2018 17:45:50 +0200 [thread overview]
Message-ID: <20180112174431-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAA2ifQycadzATfW4w0icnskOgLTB1MUT2cMxVOt4=ZMWwgL=TQ@mail.gmail.com>
On Fri, Jan 12, 2018 at 10:48:21AM +0200, Gal Hammer wrote:
>
> On Thu, Jan 11, 2018 at 9:52 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Thu, Jan 11, 2018 at 12:16:56PM +0200, Gal Hammer wrote:
> > The loading time of a VM is quite significant when its virtio
> > devices uses a large amount of virt-queues (e.g. a virtio-serial
> > device with
>
> max_ports=511). Most of the time is spend in the
> > creation of all the required event notifiers (ioeventfd and memory
> > regions).
> >
> > This patch pack all the changes to the memory regions in a
> > single memory transaction.
> >
> > Reported-by: Sitong Liu <siliu@redhat.com>
> > Reported-by: Xiaoling Gao <xiagao@redhat.com>
> > Signed-off-by: Gal Hammer <ghammer@redhat.com>
>
> Nice patch! Any timing numbers to share before/after?
>
>
> Thanks. Unfortunately I made a mistake in the shutdown code (the transaction
> is wrapping the code which doesn't modify the memory regions), so a V2 is on
> its way.
>
> As for the timing. Running a VM with 25 virtio-serial devices, each one with
> max_ports=511, results in a boot time of around 30 minutes. With this patch
> (and a another patch to kvm) reduce it to approximately 3 minutes.
Good to know, sounds like an important fix to have.
Since you plan to do v2 anyway, please add this info
in the commit log.
> This was reported and tracked here: https://bugzilla.redhat.com/show_bug.cgi?id
> =1528588
>
> Gal.
prev parent reply other threads:[~2018-01-12 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 10:16 [Qemu-devel] [PATCH] virtio: improve virtio devices initialization time Gal Hammer
2018-01-11 19:52 ` Michael S. Tsirkin
2018-01-12 8:48 ` Gal Hammer
2018-01-12 15:45 ` Michael S. Tsirkin [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=20180112174431-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ghammer@redhat.com \
--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 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.