mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Fri, 7 Oct 2005 09:44:21 -0700	[thread overview]
Message-ID: <5bdc1c8b0510070944p5a09f7f2m4965f3e0ddda21f7@mail.gmail.com> (raw)
In-Reply-To: <20051007114848.GE857@elte.hu>

On 10/7/05, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Mark Knecht <markknecht@gmail.com> wrote:
>
> > However, at odd times I still get xruns. For instance one set of xruns
> > came while browsing the web. I was on this page:
>
> > and got 2 xruns:
> >
> > 18:20:06.541 XRUN callback (8).
> > **** alsa_pcm: xrun of at least 3.172 msecs
> > **** alsa_pcm: xrun of at least 0.967 msecs
> > 18:20:07.908 XRUN callback (1 skipped).
> >
> > So, while things are far, far better for me than they were earlier
> > this week, there are still some problems I'd like to get to the bottom
> > of if possible.
>
> one thing i noticed: you have CONFIG_SMP set. Is it a true SMP x64
> system? In any case, could you try without CONFIG_SMP, just to test
> whether the latencies are related to SMP.
>
>         Ingo
>

Hi Ingo,
   OK, I've been running -rt10 for the last couple of hours on a new
kernel without SMP. No xruns so far at 64/2. I'm doing all the normal
stuff. emerge sync, building some code outside of portage, playing
music. Very good so far, but it will likely take 4-6 hours for me to
be more sure saying it was just SMP latencies.

   I see you're putting out -rt updates faster than I can build & test
them so I decided to stick with -rt10 for now to ensure a fair
comparison. I'll catch up with -rt12 or later sometime this evening to
tomorrow.

   Until then, one question. Yesterday I set priorities as such:

Jack - 80
Sound card - 80
1394 drive - 61
SATA drive 60

   What exactly do these numbers mean? If the 1394 drive was a 79
instead of a 61 would it change anything? Or does the system just
prioitize them numerically but operate on the highest numbered request
in which case a 79 vs. 61 wouldn't matter ?

Thanks,
Mark

  reply	other threads:[~2005-10-07 16:44 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
2005-10-07  2:07       ` Mark Knecht
2005-10-07 11:48         ` Ingo Molnar
2005-10-07 16:44           ` Mark Knecht [this message]
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=5bdc1c8b0510070944p5a09f7f2m4965f3e0ddda21f7@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

all inboxes | Powered by JetHome®