From: Mark Knecht <markknecht@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc3-rt10 - xruns & config questions
Date: Thu, 6 Oct 2005 13:38:33 -0700 [thread overview]
Message-ID: <5bdc1c8b0510061338r41e0b51ds2efd435a591d953e@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0510061307saf22655y26dd1e608b33a40c@mail.gmail.com>
On 10/6/05, Mark Knecht <markknecht@gmail.com> wrote:
> On 10/6/05, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Mark Knecht <markknecht@gmail.com> wrote:
> >
> > > I am still getting a few xruns even after raising Jack's priority
> > > level to 80. I am wondering whether it's fair to report these when I
> > > have CONFIG_DEBUG_PREEMPT set?
> >
> > > 4559 78 38 [IRQ 58]
> >
> > > 58: 257570 IO-APIC-level hdsp
> >
> > IRQ 58 is your audio interrupt, right? You should raise that one to prio
> > 80 too. (via chrt)
> >
> > > Since my NIC is getting a higher priority than both my sound card and
> > > my 1394 audio drives (IRQ217 vs. IRQ58/IRQ66) I assume that network
> > > activity might possibly sometimes cause a problem? Or is this not
> > > true?
> >
> > yeah, that could be the case.
> >
>
> Can you suggest how I might be able to do this at boot time?
Apologies for answering myself...
I found an old conversation that answered this, at least when I'm
logged in as root. Hopefully it will work at boot time also:
chrt -f -p 80 `pidof "IRQ 58"`
I noted that the default chrt command changed the IRQ process from
SCHED_FIFO to SCHED_RR so I assume I really should leave it at
SCHED_FIFO?
Thanks,
Mark
next prev parent reply other threads:[~2005-10-06 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 18:52 Mark Knecht
2005-10-06 19:52 ` Ingo Molnar
2005-10-06 20:07 ` Mark Knecht
2005-10-06 20:38 ` Mark Knecht [this message]
2005-10-07 2:07 ` Mark Knecht
2005-10-07 11:48 ` Ingo Molnar
2005-10-07 16:44 ` Mark Knecht
2005-10-07 17:23 ` Lee Revell
2005-10-07 17:47 ` Mark Knecht
2005-10-07 22:08 ` Lee Revell
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=5bdc1c8b0510061338r41e0b51ds2efd435a591d953e@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome