From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: Jan, "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: Linux spin lock enhancement on xen
Date: Tue, 17 Aug 2010 18:58:21 -0700 [thread overview]
Message-ID: <20100817185821.7947c500@mantra.us.oracle.com> (raw)
In-Reply-To: <4C6A64F5.E57C.0030.1@novell.com>
On Tue, 17 Aug 2010 08:34:49 -0600
"Ky Srinivasan" <ksrinivasan@novell.com> wrote:
..
> While I agree that a directed yield is a useful construct, I am not
> sure how this protocol would deal with ticket spin locks as you would
> want to implement some form of priority inheritance - if the vcpu you
> are yielding to is currently blocked on another (ticket) spin lock,
> you would want to yield to the owner of that other spin lock.
> Clearly, this dependency information is only available in the guest
> and that is where we would need to implement this logic. I think
> Jan's "enlightened" spin locks implemented this kind of logic.
Frankly, I'm opposed to ticket spin locks. IMO, starvation and fairness
are schedular problems and not of spin locks. If a vcpu has higher
priority, it is for a reason, and I'd like it to get prioritized.
Imagine a cluster stack in a 128 vcpu environment, the thread doing
heartbeat definitely needs the prirority it deserves.
Having said that, my proposal can be enhanced to take into
consideration ticket spin locks by having unlock make sure
next vcpu in line has temporary priority boost.
thanks,
Mukesh
next prev parent reply other threads:[~2010-08-18 1:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 1:33 Linux spin lock enhancement on xen Mukesh Rathor
2010-08-17 7:33 ` Keir Fraser
2010-08-17 7:53 ` Jan Beulich
2010-08-18 1:58 ` Mukesh Rathor
2010-08-17 14:34 ` Ky Srinivasan
2010-08-18 1:58 ` Mukesh Rathor [this message]
2010-08-17 17:43 ` Jeremy Fitzhardinge
2010-08-18 1:58 ` Mukesh Rathor
2010-08-18 16:37 ` Jeremy Fitzhardinge
2010-08-18 17:09 ` Keir Fraser
2010-08-19 2:52 ` Mukesh Rathor
2010-08-24 8:08 ` George Dunlap
2010-08-24 8:20 ` Keir Fraser
2010-08-24 8:43 ` George Dunlap
2010-08-24 8:48 ` Jan Beulich
2010-08-24 9:09 ` George Dunlap
2010-08-24 13:25 ` Jan Beulich
2010-08-24 16:11 ` George Dunlap
2010-08-26 14:08 ` Tim Deegan
2010-08-25 1:03 ` Dong, Eddie
2010-08-26 2:13 ` Mukesh Rathor
2010-08-19 2:52 ` Mukesh Rathor
2010-08-23 21:33 ` Jeremy Fitzhardinge
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=20100817185821.7947c500@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=ksrinivasan@novell.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).