From: Andi Kleen <andi@firstfloor.org>
To: Sergey Oboguev <oboguev.public@gmail.com>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, khalid.aziz@oracle.com
Subject: Re: [PATCH RFC] sched: deferred set priority (dprio)
Date: Sun, 3 Aug 2014 19:30:31 +0200 [thread overview]
Message-ID: <20140803173031.GQ18735@two.firstfloor.org> (raw)
In-Reply-To: <CA+80gGaohO-RaG0_tWZJEFzisrrBpgfiw-mxMrTfSK0N=k7gQA@mail.gmail.com>
> (One example might be virtual machine that runs guest operating system that is
> not paravirtualized or can be paravirtualized only to a limited extent. The VM
> might guess that preemption of VCPU thread that is processing events such as
> IPI interrupts, clock interrupts or certain device interrupts is likely to
> cause overall performance degradation due to other VCPUs spinning for an IPI
> response or spinning waiting for a spinlock, and thought the general kinds of
> these dependencies may be foreseen, but actual dependency chains between VCPUs
> cannot be established at run time.)
PAUSE loop exiting (PLE) can handle it in limited fashion on VMs
even without paravirtualization.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2014-08-03 17:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:45 [PATCH RFC] sched: deferred set priority (dprio) Sergey Oboguev
2014-07-25 20:12 ` Andy Lutomirski
2014-07-26 7:56 ` Sergey Oboguev
2014-07-26 8:58 ` Mike Galbraith
2014-07-26 18:30 ` Sergey Oboguev
2014-07-27 4:02 ` Mike Galbraith
2014-07-27 9:09 ` Sergey Oboguev
2014-07-27 10:29 ` Mike Galbraith
2014-07-28 1:19 ` Andi Kleen
2014-07-28 4:16 ` Sergey Oboguev
2014-07-28 7:24 ` Mike Galbraith
2014-08-03 0:43 ` Sergey Oboguev
2014-08-03 9:56 ` Mike Galbraith
2014-08-05 23:28 ` Sergey Oboguev
2014-08-06 5:41 ` Mike Galbraith
2014-08-06 7:42 ` Mike Galbraith
2014-08-07 1:26 ` Sergey Oboguev
2014-08-07 9:03 ` Mike Galbraith
2014-08-08 20:11 ` Sergey Oboguev
2014-08-09 13:04 ` Mike Galbraith
2014-08-09 18:04 ` Andi Kleen
2014-08-10 3:13 ` Mike Galbraith
2014-08-10 3:41 ` Mike Galbraith
2014-08-13 23:52 ` Sergey Oboguev
2014-08-09 8:38 ` Sergey Oboguev
2014-08-09 14:13 ` Mike Galbraith
2014-08-03 17:30 ` Andi Kleen [this message]
2014-08-05 23:13 ` Sergey Oboguev
2014-07-30 13:02 ` Pavel Machek
2014-08-03 0:47 ` Sergey Oboguev
2014-08-03 8:30 ` Pavel Machek
2014-08-05 23:03 ` Sergey Oboguev
-- strict thread matches above, loose matches on Subject: below --
2014-07-21 12:33 Sergey Oboguev
2014-07-21 18:14 ` Thomas Gleixner
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=20140803173031.GQ18735@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oboguev.public@gmail.com \
--cc=umgwanakikbuti@gmail.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