All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org,
	Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>,
	Ingo Molnar <mingo@elte.hu>, Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: patch] Real-Time Preemption, plist fixes
Date: Sun, 05 Jun 2005 12:53:48 +0200	[thread overview]
Message-ID: <1117968828.20785.286.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <1117960337.20785.251.camel@tglx.tec.linutronix.de>

On Sun, 2005-06-05 at 10:32 +0200, Thomas Gleixner wrote:
> On Sat, 2005-06-04 at 17:53 -0700, Daniel Walker wrote:
> > >
> > I already released a patch to fix this.
> 
> Nice to know. Where ?
> 

Ingo pointed me at the patch. 

Sorry, but I really don't see the release there.

> The first time I saw these latencies I has the PI abstraction applied, and
> the most recent time I had the attached patch applied only. This patch is
> small so I'm not sure if it could have that type of effect on task 
> latency.

It fixes a problem and uncovers others, but your comment is more a
question than an explanation for the urgency of the fix. In fact the
original implementation leads to solid deadlocks in
plist_for_each_safe() loops.


I really can't blame Ingo for ignoring this.

tglx



  reply	other threads:[~2005-06-05 10:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05  0:17 patch] Real-Time Preemption, plist fixes Thomas Gleixner
2005-06-05  0:53 ` Daniel Walker
2005-06-05  2:33   ` Plist cleanup on RT Daniel Walker
2005-06-05  8:32   ` patch] Real-Time Preemption, plist fixes Thomas Gleixner
2005-06-05 10:53     ` Thomas Gleixner [this message]
2005-06-05  7:58 ` Esben Nielsen
2005-06-05  8:05   ` Thomas Gleixner
2005-06-05  8:42     ` Esben Nielsen
2005-06-05  8:53       ` Ingo Molnar
2005-06-05  9:00         ` Esben Nielsen
2005-06-05  8:18 ` Ingo Molnar
2005-06-05  8:21   ` Thomas Gleixner
2005-06-05  8:26 ` [patch] " Ingo Molnar
2005-06-05  8:53   ` Thomas Gleixner
2005-06-05  9:47     ` Ingo Molnar
2005-06-05 15:08       ` Daniel Walker
2005-06-05  8:54   ` Esben Nielsen
2005-06-05 13:49     ` Ingo Molnar
2005-06-05 14:35       ` Esben Nielsen
2005-06-06  7:32     ` Ingo Molnar
2005-06-06  8:57       ` Esben Nielsen
2005-06-06 12:08         ` Ingo Molnar
2005-06-06 15:04       ` Daniel Walker
2005-06-05 14:51   ` Daniel Walker
2005-06-05 15:17     ` Thomas Gleixner
2005-06-05 15:21       ` Daniel Walker
2005-06-05 15:02   ` Daniel Walker
2005-06-05 16:29   ` Daniel Walker
2005-06-06  7:44     ` Ingo Molnar
2005-06-06 14:49       ` Daniel Walker

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=1117968828.20785.286.camel@tglx.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=dwalker@mvista.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@tv-sign.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.