From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
<annie.li@oracle.com>, <msw@amazon.com>
Subject: Re: [Xen-devel] [PATCH] xen/grant-table: Force to use v1 of grants.
Date: Thu, 2 Jan 2014 14:54:18 +0000 [thread overview]
Message-ID: <52C57D9A.8050804@citrix.com> (raw)
In-Reply-To: <1388502919-8601-2-git-send-email-konrad.wilk@oracle.com>
On 31/12/13 15:15, Konrad Rzeszutek Wilk wrote:
> We have the framework to use v2, but there are no backends that
> actually use it. The end result is that on PV we use v2 grants
> and on PVHVM v1. The v1 has a capacity of 512 grants per page while
> the v2 has 256 grants per page. This means we lose about 50%
> capacity - and if we want more than 16 VIFs (each VIF takes
> 512 grants), then we are hitting the max per guest of 32.
>
> Oracle-bug: 16039922
> CC: annie.li@oracle.com
> CC: msw@amazon.com
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
What does v2 add anyway? Do we want to remove all v2 related code or are
we expecting to make use of it in the near future?
David
next prev parent reply other threads:[~2014-01-02 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 15:15 Konrad Rzeszutek Wilk
2013-12-31 15:15 ` [PATCH] xen/grant-table: Force to use v1 of grants Konrad Rzeszutek Wilk
2014-01-02 14:54 ` David Vrabel [this message]
2014-01-02 19:17 ` [Xen-devel] " Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-01-16 21:22 Konrad Rzeszutek Wilk
2013-01-17 12:22 ` Matt Wilson
2013-01-17 13:05 ` [Xen-devel] " Jan Beulich
2013-01-18 2:32 ` konrad wilk
2013-01-17 13:12 ` Ian Campbell
2013-01-18 14:46 ` Konrad Rzeszutek Wilk
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=52C57D9A.8050804@citrix.com \
--to=david.vrabel@citrix.com \
--cc=annie.li@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xenproject.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