public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Calin A. Culianu" <calin@ajvar.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Shielded CPUs
Date: Wed, 14 Apr 2004 17:12:55 +0200	[thread overview]
Message-ID: <20040414151255.GA3234@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0404141111290.20579-100000@rtlab.med.cornell.edu>

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]


On Wed, Apr 14, 2004 at 11:11:47AM -0400, Calin A. Culianu wrote:
> On Wed, 14 Apr 2004, Arjan van de Ven wrote:
> 
> > On Wed, 2004-04-14 at 16:23, Calin A. Culianu wrote:
> > > This might be a bit off-topic (and might belong in the rtlinux mailing
> > > list), but I wanted people's opinion on LKML...
> > >
> > > There's an article in the May 2004 Linux Journal about some CPU affinity
> > > features in Redhawk Linux that allow a process and a set of interrupts to
> > > be locked to a particular CPU for the purposes of improving real-time
> > > performance.
> >
> > well you can do both of those already in 2.6 and in all recent vendor
> > 2.4's that I know of..... no patches needed.
> 
> 
> Cool.. it's still not, strictly speaking, _hard_ realtime, though, is it?
> Simply really good soft-realtime, right?

yep. Hard real time means you need to get a hard RT OS code. Simple as that.
And you'll always see that those cores are kept relatively small so that the
vendor can basically prove it's RT correctness.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-04-14 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 14:23 Shielded CPUs Calin A. Culianu
2004-04-14 14:38 ` Arjan van de Ven
2004-04-14 15:11   ` Calin A. Culianu
2004-04-14 15:12     ` Arjan van de Ven [this message]

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=20040414151255.GA3234@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=calin@ajvar.org \
    --cc=linux-kernel@vger.kernel.org \
    /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