From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <agnel.joel@gmail.com>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
linux-rt-users@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: RFC on fixing mutex spinning on owner
Date: Wed, 16 Mar 2016 22:17:51 -0400 [thread overview]
Message-ID: <20160316221751.71816309@grimm.local.home> (raw)
In-Reply-To: <CAD=GYpZVGwfk8Y8WTQpdgdm5qgxjsi_gVrnOswuWitEbhaWPbw@mail.gmail.com>
On Wed, 16 Mar 2016 16:38:56 -0700
Joel Fernandes <agnel.joel@gmail.com> wrote:
> I am not sure if the problem is with the i915 driver, because the
> mutex spin on owner stuff is mutex related so the mutex design may
> potentially need a tweak (I mentioned a proposal of adding mutex
> spinning time outs).
> Also since this is latency issue related (I mentioned preemptoff
> tracer and preempt disabled), I sent it to linux-rt-users. Thanks for
> the tip about sending it to i915 developers, incase no one here has a
> say in the matter, I can drop them a note later as well.
Actually, the preempt off section here is not really an issue:
rcu_read_lock();
while (owner_running(lock, owner)) {
if (need_resched())
break;
cpu_relax_lowlatency();
}
rcu_read_unlock();
Although preemption may be disabled, that "need_resched()" check will
break out of the loop if a higher priority task were to want to run on
this CPU.
I probably should add a hook there to let the preemptoff tracer know
that this is not an issue.
Thanks for the report.
-- Steve
next prev parent reply other threads:[~2016-03-17 2:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 23:22 Joel Fernandes
2016-03-16 23:35 ` Greg Kroah-Hartman
2016-03-16 23:38 ` Joel Fernandes
2016-03-17 2:17 ` Steven Rostedt [this message]
2016-03-17 5:35 ` Joel Fernandes
2016-03-17 12:08 ` Steven Rostedt
2016-03-17 7:36 ` Peter Zijlstra
2016-03-17 8:05 ` Nicholas Mc Guire
2016-03-17 10:18 ` Peter Zijlstra
2016-03-17 11:16 ` Thomas Gleixner
2016-03-17 12:06 ` Steven Rostedt
2016-03-17 12:13 ` Peter Zijlstra
2016-03-17 13:32 ` Thomas Gleixner
2016-03-17 15:36 ` Nicholas Mc Guire
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=20160316221751.71816309@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=agnel.joel@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®