mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: RFC: futex_wait() can DoS the tick
Date: Thu, 11 Jun 2015 20:52:27 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1506112052020.3786@nanos> (raw)
In-Reply-To: <1434048238.3396.59.camel@gmail.com>

On Thu, 11 Jun 2015, Mike Galbraith wrote:
> On Thu, 2015-06-11 at 15:13 +0200, Thomas Gleixner wrote:
> 
> > The kernel does not care whether the actual interrupt happens or the
> > timer is expired by other means.
> 
> Final question: Notabug explanation fits.. but why would the behavior
> delta be so radical and repeatable w/wo deadline timer on some boxen?

Good question. Cannot answer that w/o looking at traces.

Thanks,

	tglx

  reply	other threads:[~2015-06-11 18:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 12:44 Mike Galbraith
2015-06-10 15:12 ` Thomas Gleixner
2015-06-10 16:29   ` Mike Galbraith
2015-06-10 18:27     ` Thomas Gleixner
2015-06-10 17:30   ` Mike Galbraith
2015-06-10 18:59     ` Thomas Gleixner
2015-06-10 19:15       ` Steven Rostedt
2015-06-10 19:32         ` Thomas Gleixner
2015-06-11  2:27       ` Mike Galbraith
2015-06-11  8:34         ` Thomas Gleixner
2015-06-11 11:41           ` Mike Galbraith
2015-06-11 13:13             ` Thomas Gleixner
2015-06-11 13:58               ` Mike Galbraith
2015-06-11 18:43               ` Mike Galbraith
2015-06-11 18:52                 ` Thomas Gleixner [this message]
2015-06-11 18:55                   ` Mike Galbraith
2015-06-11  7:35   ` Mike Galbraith
2015-06-11  7:43     ` Mike Galbraith

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=alpine.DEB.2.11.1506112052020.3786@nanos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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
all inboxes | Powered by JetHome®