xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Kashyap Thimmaraju <kashyap.thimmaraju@sec.t-labs.tu-berlin.de>,
	xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@citrix.com>
Subject: Re: Deployment usage and performance of a network domain
Date: Wed, 14 Jun 2017 10:10:08 +0200	[thread overview]
Message-ID: <1497427808.26212.47.camel@citrix.com> (raw)
In-Reply-To: <593E4E6E.7020303@sec.t-labs.tu-berlin.de>


[-- Attachment #1.1: Type: text/plain, Size: 1854 bytes --]

On Mon, 2017-06-12 at 10:18 +0200, Kashyap Thimmaraju wrote:
> > Driver domains and stubdomains are hugely used in contexts
> > targeting really strong security, like Qubes and OpenXT:
> > 
> > https://www.qubes-os.org/ http://openxt.org/
> > 
> > Qubes targets laptops. I've tried it on mine, which is quite old,
> > and the drop in perf, e.g., wrt a regular (as in, one that does not
> > use virtualization at all) Linux desktop, although present, I don't
> > think it comes too much from the driver domain(s).
> > 
> > I haven't run any benchmarks with it, but despite (as I said) the 
> > laptop being quite old, the system is definitely usable.
> 
> Thanks. I looked for a performance evaluation of such an architecture
> but did not find anything. It would be good to know if there are some
> meaningful numbers. 
>
Well, I don't know of any either, but I have never looked. Fact is,
meaningfulness depends on what each of us needs and actually find
meaningful. So, it's entirely possible that no one has preformed before
the specific evaluation you would like to see...

> The openxt example of having dedicated virtual
> network domains for clients is indeed a good one but I could not find
> any performance evaluation on that. Would you or anybody here happen
> to know where I can find such information? The 2016 summit does not
> have anything on it either.
>
I think you should:
 - ask them directly,
 - begin considering doing some evaluation yourself. If you do, we're
   definitely interested in seeing what you will find out.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-06-14  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 12:32 Deployment usage and performance of a network domain Kashyap Thimmaraju
2017-06-08 17:07 ` Dario Faggioli
2017-06-12  8:18   ` Kashyap Thimmaraju
2017-06-14  8:10     ` Dario Faggioli [this message]
2017-06-14  8:13       ` Kashyap Thimmaraju

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=1497427808.26212.47.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=kashyap.thimmaraju@sec.t-labs.tu-berlin.de \
    --cc=xen-devel@lists.xen.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).