From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
"Keir (Xen.org)" <keir@xen.org>,
"jbeulich@suse.com" <jbeulich@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
"zhiyuan.lv@intel.com" <zhiyuan.lv@intel.com>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH 3/3] tools: introduce parameter max_ranges.
Date: Tue, 19 Jan 2016 15:04:00 +0000 [thread overview]
Message-ID: <20160119150400.GK1691@citrix.com> (raw)
In-Reply-To: <968fc8fc8f824ee7903fe7c8cbb7b5c0@AMSPEX02CL03.citrite.net>
On Tue, Jan 19, 2016 at 02:47:40PM +0000, Paul Durrant wrote:
[...]
> > ranges so perhaps the parameter name could be
> > 'max_wp_memory_ranges'?
> > >
> >
> > What does "WP" mean? "Write Protected"?
> >
>
> Yes.
>
> > Is this parameter closely related to IOREQ server? Should it contain
> > "ioreq" somehow?
> >
>
> It is closely related but ioreq server is an implementation detail so
> do we want to expose it as a tunable? The concept we need to capture
> is that the toolstack can tune the limit of the maximum number of
> pages in the VM that can be set such that writes are emulated (but
> reads are as for normal ram). Or I guess we could get very specific
> and call it something like 'max_gtt_shadows'?
I would prefer generic concept in this case ("wp"). Let's wait a bit for
other people to voice their opinion.
Whichever one we pick it the meaning of the acronym needs to be clearly
documented...
Wei.
>
> > Wei.
next prev parent reply other threads:[~2016-01-19 15:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 9:27 [PATCH v10 0/3] Refactor ioreq server for better performance Yu Zhang
2016-01-19 9:27 ` [PATCH v10 1/3] Refactor rangeset structure " Yu Zhang
2016-01-19 9:27 ` [PATCH v10 2/3] Differentiate IO/mem resources tracked by ioreq server Yu Zhang
2016-01-19 9:47 ` Paul Durrant
2016-01-19 9:27 ` [PATCH 3/3] tools: introduce parameter max_ranges Yu Zhang
2016-01-19 11:53 ` Wei Liu
2016-01-19 13:54 ` Paul Durrant
2016-01-19 14:37 ` Wei Liu
2016-01-19 14:47 ` Paul Durrant
2016-01-19 15:04 ` Wei Liu [this message]
2016-01-19 15:18 ` Ian Campbell
2016-01-20 3:14 ` Tian, Kevin
2016-01-20 3:33 ` Yu, Zhang
2016-01-20 3:58 ` Tian, Kevin
2016-01-20 5:02 ` Yu, Zhang
2016-01-20 10:17 ` Wei Liu
2016-01-20 10:16 ` Ian Campbell
2016-01-20 10:18 ` Paul Durrant
2016-01-20 11:13 ` Yu, Zhang
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=20160119150400.GK1691@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yu.c.zhang@linux.intel.com \
--cc=zhiyuan.lv@intel.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 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).