All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Paul Moore <paul.moore@hp.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	James Carter <jwcart2@tycho.nsa.gov>,
	Eric Paris <eparis@parisplace.org>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>,
	"Christopher J. PeBenito" <cpebenito@tresys.com>,
	Joshua Brindle <method@manicmethod.com>,
	KaiGai Kohei <kaigai@kaigai.gr.jp>
Subject: Re: [bug] very high non-preempt latency in context_struct_compute_av()
Date: Mon, 4 Jun 2007 18:54:33 -0400 (EDT)	[thread overview]
Message-ID: <Line.LNX.4.64.0706041853210.14560@d.namei> (raw)
In-Reply-To: <200706041848.21306.paul.moore@hp.com>

On Mon, 4 Jun 2007, Paul Moore wrote:

> Okay, for some reason I thought someone had found a way to make 
> RCU "preemptable" through the real-time work, maybe I'm just confused 
> again :)

It is preemptible in the RT kernel, but as Ingo points out, nothing should 
be even trying to do something for 130ms in the kernel.


- James
-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2007-06-04 22:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 11:27 [bug] very high non-preempt latency in context_struct_compute_av() Ingo Molnar
2007-06-04 13:25 ` James Morris
2007-06-04 14:17   ` Ingo Molnar
2007-06-04 21:11 ` Paul Moore
2007-06-04 21:39   ` Stephen Smalley
2007-06-04 22:48     ` Paul Moore
2007-06-04 22:54       ` James Morris [this message]
2007-06-07 19:34 ` Stephen Smalley
2007-06-07 19:51   ` Ingo Molnar
2007-06-07 20:11     ` James Morris

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=Line.LNX.4.64.0706041853210.14560@d.namei \
    --to=jmorris@namei.org \
    --cc=akpm@linux-foundation.org \
    --cc=cpebenito@tresys.com \
    --cc=eparis@parisplace.org \
    --cc=jwcart2@tycho.nsa.gov \
    --cc=kaigai@kaigai.gr.jp \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=method@manicmethod.com \
    --cc=mingo@elte.hu \
    --cc=paul.moore@hp.com \
    --cc=sds@tycho.nsa.gov \
    /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.