From: "Gao, Ping A" <ping.a.gao@intel.com>
To: kwankhede@nvidia.com, alex.williamson@redhat.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Jike Song <jike.song@intel.com>
Subject: [RFC]Add new mdev interface for QoS
Date: Wed, 26 Jul 2017 21:16:59 +0800 [thread overview]
Message-ID: <9951f9cf-89dd-afa4-a9f7-9a795e4c01af@intel.com> (raw)
The vfio-mdev provide the capability to let different guest share the
same physical device through mediate sharing, as result it bring a
requirement about how to control the device sharing, we need a QoS
related interface for mdev to management virtual device resource.
E.g. In practical use, vGPUs assigned to different quests almost has
different performance requirements, some guests may need higher priority
for real time usage, some other may need more portion of the GPU
resource to get higher 3D performance, corresponding we can define some
interfaces like weight/cap for overall budget control, priority for
single submission control.
So I suggest to add some common attributes which are vendor agnostic in
mdev core sysfs for QoS purpose.
-Ping
next reply other threads:[~2017-07-26 13:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 13:16 Gao, Ping A [this message]
2017-07-26 16:43 ` [RFC]Add new mdev interface for QoS Alex Williamson
2017-07-27 16:00 ` Gao, Ping A
2017-08-01 5:54 ` Gao, Ping A
2017-08-01 22:26 ` Alex Williamson
2017-08-02 2:50 ` Tian, Kevin
2017-08-02 10:19 ` Kirti Wankhede
2017-08-02 12:59 ` Gao, Ping A
2017-08-02 15:46 ` Kirti Wankhede
2017-08-02 16:58 ` Alex Williamson
2017-08-03 12:26 ` Gao, Ping A
2017-08-03 21:11 ` Alex Williamson
2017-08-07 7:41 ` Gao, Ping A
2017-08-08 6:42 ` Kirti Wankhede
2017-08-08 12:48 ` Gao, Ping A
2017-07-27 16:17 ` [libvirt] " Daniel P. Berrange
2017-07-27 18:01 ` Alex Williamson
2017-07-28 8:10 ` Daniel P. Berrange
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=9951f9cf-89dd-afa4-a9f7-9a795e4c01af@intel.com \
--to=ping.a.gao@intel.com \
--cc=alex.williamson@redhat.com \
--cc=jike.song@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyuw@linux.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).