All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.X, NPTL, SCHED_FIFO and JACK
Date: Wed, 30 Jun 2004 17:18:57 +0200	[thread overview]
Message-ID: <20040630151857.GA29070@elte.hu> (raw)
In-Reply-To: <20040630150430.GA28506@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> A simple "strace -f" should show whether the setscheduler() call
> succeeds or not. Does 'jackstart' do anything with glibc internals?

it seems part of the problem is that the setscheduler() calls 'succeed',
but the policy is not changed to SCHED_FIFO. The question here is, 
are the correct PIDs used?

	Ingo

  reply	other threads:[~2004-06-30 15:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 13:41 2.6.X, NPTL, SCHED_FIFO and JACK Paul Davis
2004-06-30 15:04 ` Ingo Molnar
2004-06-30 15:18   ` Ingo Molnar [this message]
2004-06-30 15:26   ` Jakub Jelinek
2004-06-30 16:32     ` Paul Davis
2004-06-30 16:57       ` Jakub Jelinek
2004-06-30 17:52         ` Paul Davis
2004-06-30 15:05 ` Ingo Molnar
2004-06-30 16:12   ` Paul Davis
2004-06-30 17:07     ` Ulrich Drepper
2004-06-30 17:50       ` Paul Davis
2004-07-01 18:03 ` Matt Mackall
2004-07-01 18:14   ` William Lee Irwin III
2004-07-01 22:45     ` Andrew Morton
2004-07-02  0:45       ` William Lee Irwin III
2004-07-02  1:38         ` Peter Williams
2004-07-02  2:53           ` William Lee Irwin III
2004-07-02  3:03         ` Con Kolivas
2004-07-02  3:05           ` William Lee Irwin III
2004-07-02  3:27     ` Paul Davis
2004-07-02  7:37       ` William Lee Irwin III
2004-07-02 10:40         ` Takashi Iwai
2004-07-06  0:48           ` Peter Williams
2004-07-02 14:42         ` Paul Davis

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=20040630151857.GA29070@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@linuxaudiosystems.com \
    /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.