mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc2-rt7 - AMD64 runs GREAT! (threaded/non-threaded interrupts?)
Date: Fri, 30 Sep 2005 09:14:19 -0700	[thread overview]
Message-ID: <5bdc1c8b0509300914qb1b436eqec6df8e87d110182@mail.gmail.com> (raw)
In-Reply-To: <1128096321.12850.16.camel@c-67-188-6-232.hsd1.ca.comcast.net>

On 9/30/05, Daniel Walker <dwalker@mvista.com> wrote:
> On Fri, 2005-09-30 at 08:54 -0700, Mark Knecht wrote:
> > Hi,
> >    I finally managed to find an acceptable set of config options last
> > even that build correctly. The kernel came right up and is working
> > wonderfully on my Gentoo system. I've been up for a few hours this
> > morning with Jack going at 128/2. (<6mS latency) Music is streaming
> > with no xruns, even while doing emerge sync/emerge world operations.
> >
> >
> >    One question. In earlier rt kernels there was a way to set specific
> > ISR routinges as threaded or non-threaded through
> > /proc/irq/ISR#/DEVICE/threaded. Does anything like this exist anymore?
>
> I think there was a way to select softirqd as thread or not. This
> doesn't exist for interrupts because the ISR would need to be modified
> at compile time to work correctly. So you can't simple select drivers to
> run in interrupt context unless they are specifically written to do so.
>
> Daniel

I'll keep that in mind over the next few days. So far this is running
very, very well, although the testing is still young.

I was beginning to wonder if this machine was going to be useful. I'm
now far more confident.

Cheers and out,
Mark

      reply	other threads:[~2005-09-30 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 15:54 Mark Knecht
2005-09-30 16:05 ` Daniel Walker
2005-09-30 16:14   ` Mark Knecht [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=5bdc1c8b0509300914qb1b436eqec6df8e87d110182@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=dwalker@mvista.com \
    --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

all inboxes | Powered by JetHome®