From: "Yu, Zhang" <yu.c.zhang@linux.intel.com>
To: xen-devel@lists.xenproject.org, keir@xen.org, JBeulich@suse.com,
andrew.cooper3@citrix.com, Paul.Durrant@citrix.com
Cc: kevin.tian@intel.com, zhiyuan.lv@intel.com
Subject: Re: [PATCH 0/2] Refactor ioreq server for better performance.
Date: Thu, 02 Jul 2015 23:07:47 +0800 [thread overview]
Message-ID: <559553C3.1090703@linux.intel.com> (raw)
In-Reply-To: <1435840294-22114-1-git-send-email-yu.c.zhang@linux.intel.com>
Oh, I forgot the version number and change history.
This patchset should be version 2.
The change history should be:
1> Split the original patch into 2;
2> Take Paul Durrant’s comments:
a> Add a name member in the struct rb_rangeset, and use the ‘q’
debug key to dump the ranges in ioreq server;
b> Keep original routine names for hvm ioreq server;
c>. Commit message changes – mention that a future patch to change
the maximum ranges inside ioreq server;
Sorry, my fault. Could I add this change history in next version,
or should I resend the version 2? :)
Thanks
Yu
On 7/2/2015 8:31 PM, Yu Zhang wrote:
> XenGT leverages ioreq server to track and forward the accesses to
> GPU I/O resources, e.g. the PPGTT(per-process graphic translation
> tables). Currently, ioreq server uses rangeset to track the BDF/
> PIO/MMIO ranges to be emulated. To select an ioreq server, the
> rangeset is searched to see if the I/O range is recorded. However,
> traversing the link list inside rangeset could be time consuming
> when number of ranges is too high. On HSW platform, number of PPGTTs
> for each vGPU could be several hundred. On BDW, this value could
> be several thousand.
>
> To accommodate more ranges, limitation of the number of ranges in an
> ioreq server, MAX_NR_IO_RANGES is changed - future patches will be
> provided to tune this with other approaches. And to increase the ioreq
> server performance, a new data structure, rb_rangeset, is introduced.
>
> Yu Zhang (2):
> Resize the MAX_NR_IO_RANGES for ioreq server
> Add new data structure to track ranges.
>
> xen/arch/x86/domain.c | 3 +
> xen/arch/x86/hvm/hvm.c | 56 ++++++--
> xen/common/Makefile | 1 +
> xen/common/rb_rangeset.c | 281 +++++++++++++++++++++++++++++++++++++++
> xen/include/asm-x86/hvm/domain.h | 4 +-
> xen/include/asm-x86/hvm/hvm.h | 1 +
> xen/include/xen/rb_rangeset.h | 49 +++++++
> 7 files changed, 379 insertions(+), 16 deletions(-)
> create mode 100644 xen/common/rb_rangeset.c
> create mode 100644 xen/include/xen/rb_rangeset.h
>
next prev parent reply other threads:[~2015-07-02 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 12:31 [PATCH 0/2] Refactor ioreq server for better performance Yu Zhang
2015-07-02 12:31 ` [PATCH 1/2] Resize the MAX_NR_IO_RANGES for ioreq server Yu Zhang
2015-07-02 12:31 ` [PATCH 2/2] Add new data structure to track ranges Yu Zhang
2015-07-02 15:07 ` Yu, Zhang [this message]
2015-07-06 7:09 ` [PATCH 0/2] Refactor ioreq server for better performance 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=559553C3.1090703@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
--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 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.