From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <GHaskins@novell.com>
Cc: mst@redhat.com, mingo@elte.hu, gregory.haskins@gmail.com,
alacrityvm-devel@lists.sourceforge.net, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model for vbus_drive
Date: Tue, 18 Aug 2009 15:19:53 +0300 [thread overview]
Message-ID: <4A8A9C69.6060900@redhat.com> (raw)
In-Reply-To: <4A8A62370200005A000528DF@sinclair.provo.novell.com>
On 08/18/2009 03:11 PM, Gregory Haskins wrote:
> Sorry for the toppost. Still not at the office.
>
> I just wanted to add that we've already been through this disussion once. (Search "haskins hypercall lkml" on google and I'm sure you are bound to see hits.
>
>
Your numbers showed a 350ns difference on fairly old (by now) hardware.
I doubt the difference will exceed 200ns now.
> The fact is: the original vbus was designed with hypercalls, and it drew much of these same critisims. In the end, hypercalls are only marginally faster than PIO (iirc, 450ns faster, and shrinking), so we decided that it was not worth further discussion at the time.
>
Has anything changed?
> A better solution is probably PIOoHC, so that you retain the best properties of both. The only problem with the entire PIOx approach is that its x86 specific, but that is an entirely different thread.
>
pio is nicely abstracted by PCI. virtio-pci will use pio on x86 and
mmio on non-x86.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-08-18 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A8A622E0200005A000528DC@sinclair.provo.novell.com>
2009-08-18 12:11 ` [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model for vbus_drive Gregory Haskins
2009-08-18 12:19 ` Avi Kivity [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=4A8A9C69.6060900@redhat.com \
--to=avi@redhat.com \
--cc=GHaskins@novell.com \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=gregory.haskins@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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).