xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: therion@ninth-art.de
Cc: xen-devel@lists.xensource.com
Subject: Re: Fwd: Re:  Xen 4.3 / 4.4 - concurrent APIs, VGA Passthru
Date: Mon, 18 Aug 2014 16:45:45 +0100	[thread overview]
Message-ID: <53F21FA9.7040103@bobich.net> (raw)
In-Reply-To: <53F21B20.90108@ninth-art.de>

On 08/18/2014 04:26 PM, Georg Bege wrote:
> Hi
>
> I simply wanted to tell my tale about the outcome of my experiments,
> I was occupied with certain other things (including exchanging some
> zpool's).
> For now I run an Vista x64 and it works pretty well, I never got the
> gplpv drivers running on
> acceptable levels (they are still quite slow) so I decided to pass
> onboard controller, sound and usb3.
> This decission seemed to be a wise one and everything works great as
> expected, the problem with gplpv
> well it might also be a result of my volume scheme since I only run ZFS
> - now an raidz1 (on enterprise disks though).
> I also replaced the nvidia drivers from 331.65 to 337.88 - this revision
> gave me a lot more performance but I can remember I had this issue on
> native Windows too.
>
> So after a lot of testing, pain, time consuming days (and nights) its
> really working great - not perfect maybe.
> My next goal is to dedicate an SSD for that system volume, maybe try
> Win7 again as well -
> also I'd like to get an GTX690 and hardmod it so I get a lot more speed...

Modifying it won't get you more speed.

I was originally planning to use a GTX690 and pass one GPU to each of my 
VMs, but I eventually replaced it with a pair of 780Tis.

I am running on a SSD backed zvol, with gplpv.

Gordan

  reply	other threads:[~2014-08-18 15:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53D5C00E.5040706@ninth-art.de>
2014-07-28 14:10 ` Fwd: Re: Xen 4.3 / 4.4 - concurrent APIs, VGA Passthru Georg Bege
2014-07-28 14:34   ` jacek burghardt
2014-07-28 15:01   ` Gordan Bobic
     [not found]     ` <53D6F500.1010806@ninth-art.de>
     [not found]       ` <53D748DC.10209@bobich.net>
     [not found]         ` <53D74F9E.6010508@ninth-art.de>
     [not found]           ` <bb4d5eb4f453e5596f696eb93c3f7df5@mail.shatteredsilicon.net>
2014-07-29 11:52             ` Georg Bege
2014-07-29 12:22               ` Gordan Bobic
2014-08-02 10:49                 ` Georg Bege
2014-08-03  9:49                   ` Gordan Bobic
     [not found]                     ` <53DE0A73.9040304@ninth-art.de>
2014-08-03 10:20                       ` Fwd: " Georg Bege
2014-08-04  8:18                       ` Gordan Bobic
2014-08-04 19:30                         ` Georg Bege
2014-08-18 15:26                         ` Georg Bege
2014-08-18 15:45                           ` Gordan Bobic [this message]
2014-08-18 21:13                             ` Richie
2014-08-19 10:31                               ` Gordan Bobic
2014-08-03  9:57                   ` James Harper
2014-08-03  1:09             ` Georg Bege
2014-08-03  9:40               ` Gordan Bobic

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=53F21FA9.7040103@bobich.net \
    --to=gordan@bobich.net \
    --cc=therion@ninth-art.de \
    --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 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).