From: Juergen Gross <jgross@suse.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Bob Liu <bob.liu@oracle.com>,
xen-devel@lists.xenproject.org, paul.durrant@citrix.com,
david.vrabel@citrix.com, roger.pau@citrix.com,
linux-kernel@vger.kernel.org, konrad.wilk@oracle.com,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH RESEND 1/2] xenbus_client: Extend interface to support multi-page ring
Date: Tue, 31 Mar 2015 15:16:33 +0200 [thread overview]
Message-ID: <551A9E31.2030304@suse.com> (raw)
In-Reply-To: <20150331131335.GC14300@zion.uk.xensource.com>
On 03/31/2015 03:13 PM, Wei Liu wrote:
> On Tue, Mar 31, 2015 at 02:36:43PM +0200, Juergen Gross wrote:
>> On 03/31/2015 02:15 PM, Bob Liu wrote:
>>> From: Wei Liu <wei.liu2@citrix.com>
>>>
>>> Originally Xen PV drivers only use single-page ring to pass along
>>> information. This might limit the throughput between frontend and
>>> backend.
>>>
>>> The patch extends Xenbus driver to support multi-page ring, which in
>>> general should improve throughput if ring is the bottleneck. Changes to
>>> various frontend / backend to adapt to the new interface are also
>>> included.
>>>
>>> Affected Xen drivers:
>>> * blkfront/back
>>> * netfront/back
>>> * pcifront/back
>>
>> What about pvscsi drivers?
>> They are affected, too!
>>
>
> When I wrote this patch pvscsi didn't exist upstream.
>
> It would be fairly easy to change that driver too.
Sure. But if you don't do it you'll break the build...
Juergen
next prev parent reply other threads:[~2015-03-31 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 12:15 Bob Liu
2015-03-31 12:15 ` [PATCH v2 2/2] xen/block: add multi-page ring support Bob Liu
2015-04-01 11:51 ` Bob Liu
2015-04-01 14:55 ` Konrad Rzeszutek Wilk
2015-03-31 12:36 ` [PATCH RESEND 1/2] xenbus_client: Extend interface to support multi-page ring Juergen Gross
2015-03-31 13:13 ` Wei Liu
2015-03-31 13:16 ` Juergen Gross [this message]
2015-03-31 23:06 ` Bob Liu
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=551A9E31.2030304@suse.com \
--to=jgross@suse.com \
--cc=bob.liu@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome