All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, TimDeegan <tim@xen.org>,
	Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: RFC Userspace hypercalls
Date: Wed, 6 Jan 2016 17:06:11 +0000	[thread overview]
Message-ID: <568D4983.5030907@citrix.com> (raw)
In-Reply-To: <568D53B202000078000C41CC@prv-mh.provo.novell.com>

On 06/01/16 16:49, Jan Beulich wrote:
>>>> On 06.01.16 at 17:38, <andrew.cooper3@citrix.com> wrote:
>> On 06/01/16 16:31, Jan Beulich wrote:
>>>>>> On 06.01.16 at 15:44, <andrew.cooper3@citrix.com> wrote:
>>>> We did have an internal request for an HVM guest userspace netfront
>>>> driver to be able to use evntchnop calls directly.
>>> And this can't be accomplished using the evtchn and/or privcmd
>>> drivers?
>> It can, and I don't believe the worry about extra overhead is well
>> placed.  (There many areas of lower hanging fruit in this specific case).
>>
>> However, a userspace backend isn't in principle a bad idea.
> Backend? Earlier you said frontend.

I did mean frontend, but it really doesn't matter as far as this is
concerned.

> Nor can I see how using the evtchn/privcmd devices would preclude that.

They don't.  I didn't imply that they would.

> After all their purpose is to avoid having to expose hypercalls directly.

Only one purpose.  Another purpose is to enforce separation between
processes, and handle allocation of global resources.

In a dedicated utility VM, where all components are trusted, none of
these reasons have as much weight as they do in a general purpose OS,
and there is a valid argument to be made for favouring performance over
isolation.

I am not suggesting that userspace hypercalls would make orders of
magnitude difference, but they would make some difference, and allow a
Xen domain to have a more rDMA-like approach, if it chooses.

~Andrew

  reply	other threads:[~2016-01-06 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 11:44 RFC Userspace hypercalls Andrew Cooper
2016-01-06 14:14 ` Jan Beulich
2016-01-06 14:44   ` Andrew Cooper
2016-01-06 16:09     ` Jan Beulich
2016-01-06 16:20       ` Andrew Cooper
2016-01-06 16:24         ` Jan Beulich
2016-01-06 16:31     ` Jan Beulich
2016-01-06 16:38       ` Andrew Cooper
2016-01-06 16:49         ` Jan Beulich
2016-01-06 17:06           ` Andrew Cooper [this message]
2016-01-06 16:41       ` David Vrabel
2016-01-07 10:42 ` Ian Campbell
2016-01-07 10:55   ` Andrew Cooper

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=568D4983.5030907@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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 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.