From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xensource.com,
Ian.Campbell@citrix.com
Subject: Re: [PATCH v3 1/5] xen: introduce two different max_nr_dom0/domU_grant_frames parameters
Date: Thu, 9 Oct 2014 10:35:55 +0100 [thread overview]
Message-ID: <543656FB.8040202@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410081758510.17038@kaball.uk.xensource.com>
On 08/10/14 17:59, Stefano Stabellini wrote:
> On Wed, 8 Oct 2014, David Vrabel wrote:
>> On 08/10/14 17:01, Stefano Stabellini wrote:
>>> On Wed, 8 Oct 2014, David Vrabel wrote:
>>>> On 08/10/14 14:00, Stefano Stabellini wrote:
>>>>> Remove max_nr_grant_frames, both variable and preprocessor symbol.
>>>>> Introduce two global variables max_nr_dom0_grant_frames and
>>>>> max_nr_domU_grant_frames, separately configurable via the Xen command line
>>>>> option "gnttab_max_nr_frames".
>>>>
>>>> Why? I can't think of a sensible use case for this and you don't list
>>>> one. dom0 doesn't really use grants so its current number grant frames
>>>> is usually 1 so it doesn't seem useful to restrict it differently.
>>>
>>> See the recent discussion with Jan:
>>>
>>> http://marc.info/?l=xen-devel&m=141260825209210
>>
>> I still don't see a use case. Either:
>>
>> a) dom0 is the driver domain and doesn't need a large number of grants.
>>
>> or
>>
>> b) dom0 has a frontend driver, then the driver domain will have to scan
>> dom0's grant table thus dom0's grant table must be sized the same as domUs.
>
> I don't have an opinion on this, so I'll leave it up to you and Jan to
> come to an agreement.
I don't feel strongly on this so I'll defer to Jan.
David
next prev parent reply other threads:[~2014-10-09 9:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 12:58 [PATCH v3 0/5] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-08 13:00 ` [PATCH v3 1/5] xen: introduce two different max_nr_dom0/domU_grant_frames parameters Stefano Stabellini
2014-10-08 15:15 ` David Vrabel
2014-10-08 16:01 ` Stefano Stabellini
2014-10-08 16:42 ` David Vrabel
2014-10-08 16:59 ` Stefano Stabellini
2014-10-09 9:35 ` David Vrabel [this message]
2014-10-10 7:35 ` Jan Beulich
2014-10-10 9:19 ` David Vrabel
2014-10-10 7:37 ` Jan Beulich
2014-10-08 13:00 ` [PATCH v3 2/5] xen/arm: introduce invalidate_xen_dcache_va_range Stefano Stabellini
2014-10-08 13:00 ` [PATCH v3 3/5] xen/x86: introduce more cache maintenance operations Stefano Stabellini
2014-10-10 7:40 ` Jan Beulich
2014-10-10 9:23 ` Stefano Stabellini
2014-10-10 9:45 ` Jan Beulich
2014-10-08 13:00 ` [PATCH v3 4/5] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-08 15:02 ` Andrew Cooper
2014-10-10 7:56 ` Jan Beulich
2014-10-08 13:00 ` [PATCH v3 5/5] Revert "xen/arm: introduce XENFEAT_grant_map_identity" Stefano Stabellini
2014-10-08 14:06 ` Julien Grall
2014-10-09 10:36 ` Stefano Stabellini
2014-10-08 15:42 ` [PATCH v3 0/5] xen/arm: introduce GNTTABOP_cache_flush David Vrabel
2014-10-09 10:22 ` 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=543656FB.8040202@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.