All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	xen-devel@lists.xensource.com
Cc: julien.grall@citrix.com, Ian.Campbell@citrix.com
Subject: Re: [PATCH v6 6/8] xen/arm: introduce GNTTABOP_cache_flush
Date: Thu, 16 Oct 2014 18:03:05 +0100	[thread overview]
Message-ID: <543FFA49.60101@citrix.com> (raw)
In-Reply-To: <1413470755-30991-6-git-send-email-stefano.stabellini@eu.citrix.com>

On 16/10/14 15:45, Stefano Stabellini wrote:
> Introduce a new hypercall to perform cache maintenance operation on
> behalf of the guest. The argument is a machine address and a size. The
> implementation checks that the memory range is owned by the guest or the
> guest has been granted access to it by another domain.
> 
> Introduce grant_map_exists: an internal grant table function to check
> whether an mfn has been granted to a given domain on a target grant
> table.
> 
> As grant_map_exists loops over all the guest grant table entries, limit
> DEFAULT_MAX_NR_GRANT_FRAMES to 10 to cap the loop to 5000 iterations
> max. Warn if the user sets max_grant_frames higher than 10.

No.  This is much too low.

A netfront with 4 queues wants 4 * 2 * 256 = 2048 grant references. So
this limit would only allow for two VIFs which is completely unacceptable.

blkfront would be similarly constrained.

I think you're going to have to add continuations somehow or you are
going to have abandon this approach and use the SWIOTLB in the guest.

David

  parent reply	other threads:[~2014-10-16 17:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 14:44 [PATCH v6 0/8] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-16 14:45 ` [PATCH v6 1/8] xen: introduce gnttab_max_frames and gnttab_max_maptrack_frames command line options Stefano Stabellini
2014-10-16 16:15   ` Jan Beulich
2014-10-16 16:56     ` Stefano Stabellini
2014-10-16 16:57       ` Stefano Stabellini
2014-10-17  8:44       ` Jan Beulich
2014-10-16 14:45 ` [PATCH v6 2/8] xen/arm: rename *_xen_dcache_* operations to *_dcache_* Stefano Stabellini
2014-10-16 14:45 ` [PATCH v6 3/8] xen/arm: return int *_dcache_va_range Stefano Stabellini
2014-10-16 15:06   ` Julien Grall
2014-10-16 14:45 ` [PATCH v6 4/8] xen/arm: introduce invalidate_dcache_va_range Stefano Stabellini
2014-10-16 14:45 ` [PATCH v6 5/8] xen/x86: introduce more cache maintenance operations Stefano Stabellini
2014-10-16 16:18   ` Jan Beulich
2014-10-16 14:45 ` [PATCH v6 6/8] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-16 16:25   ` Jan Beulich
2014-10-16 16:30     ` Stefano Stabellini
2014-10-17  8:46       ` Jan Beulich
2014-10-16 17:03   ` David Vrabel [this message]
2014-10-16 17:29     ` Stefano Stabellini
2014-10-16 17:47       ` David Vrabel
2014-10-17 10:01         ` Stefano Stabellini
2014-10-17 10:23           ` Jan Beulich
2014-10-17  9:44       ` Jan Beulich
2014-10-16 14:45 ` [PATCH v6 7/8] Revert "xen/arm: introduce XENFEAT_grant_map_identity" Stefano Stabellini
2014-10-16 14:45 ` [PATCH v6 8/8] Revert "xen: introduce arch_grant_(un)map_page_identity" Stefano Stabellini

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=543FFA49.60101@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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.