From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paul Durrant <paul.durrant@citrix.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [Qemu-devel] [PATCH v3] xen-disk: use an IOThread per instance
Date: Wed, 8 Nov 2017 17:45:06 +0000 [thread overview]
Message-ID: <20171108174506.GI12670@redhat.com> (raw)
In-Reply-To: <20171108174227.GC8403@stefanha-x1.localdomain>
On Wed, Nov 08, 2017 at 05:42:27PM +0000, Stefan Hajnoczi wrote:
> On Tue, Nov 07, 2017 at 05:46:53AM -0500, Paul Durrant wrote:
> > This patch allocates an IOThread object for each xen_disk instance and
> > sets the AIO context appropriately on connect. This allows processing
> > of I/O to proceed in parallel.
> >
> > The patch also adds tracepoints into xen_disk to make it possible to
> > follow the state transtions of an instance in the log.
>
> virtio-blk and virtio-scsi allow the user to specify an IOThread object.
> This allows users to configure the device<->IOThread mapping any way
> they like (e.g. 1:1, M:N). Are you sure you want to hard-code the
> IOThread mapping?
I certainly think it'd be better for mgmt apps if all disks had the same
approach to IOThread mapping.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Paul Durrant <paul.durrant@citrix.com>,
Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [Qemu-devel] [PATCH v3] xen-disk: use an IOThread per instance
Date: Wed, 8 Nov 2017 17:45:06 +0000 [thread overview]
Message-ID: <20171108174506.GI12670@redhat.com> (raw)
In-Reply-To: <20171108174227.GC8403@stefanha-x1.localdomain>
On Wed, Nov 08, 2017 at 05:42:27PM +0000, Stefan Hajnoczi wrote:
> On Tue, Nov 07, 2017 at 05:46:53AM -0500, Paul Durrant wrote:
> > This patch allocates an IOThread object for each xen_disk instance and
> > sets the AIO context appropriately on connect. This allows processing
> > of I/O to proceed in parallel.
> >
> > The patch also adds tracepoints into xen_disk to make it possible to
> > follow the state transtions of an instance in the log.
>
> virtio-blk and virtio-scsi allow the user to specify an IOThread object.
> This allows users to configure the device<->IOThread mapping any way
> they like (e.g. 1:1, M:N). Are you sure you want to hard-code the
> IOThread mapping?
I certainly think it'd be better for mgmt apps if all disks had the same
approach to IOThread mapping.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-08 17:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 10:46 [Qemu-devel] [PATCH v3] xen-disk: use an IOThread per instance Paul Durrant
2017-11-07 10:46 ` Paul Durrant
2017-11-08 17:42 ` [Qemu-devel] " Stefan Hajnoczi
2017-11-08 17:42 ` Stefan Hajnoczi
2017-11-08 17:45 ` Daniel P. Berrange [this message]
2017-11-08 17:45 ` Daniel P. Berrange
2017-11-09 9:30 ` Paul Durrant
2017-11-09 9:30 ` Paul Durrant
2017-11-09 11:17 ` Stefan Hajnoczi
2017-11-09 11:17 ` Stefan Hajnoczi
2017-11-15 9:48 ` Paul Durrant
2017-11-15 9:48 ` Paul Durrant
2017-11-16 1:11 ` [Qemu-devel] " Stefano Stabellini
2017-11-16 1:11 ` Stefano Stabellini
2017-11-16 9:44 ` [Qemu-devel] " Paul Durrant
2017-11-16 9:44 ` Paul Durrant
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=20171108174506.GI12670@redhat.com \
--to=berrange@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=stefanha@gmail.com \
--cc=xen-devel@lists.xenproject.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.