mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jack O'Quin" <joq@io.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	rlrevell@joe-job.com, paul@linuxaudiosystems.com,
	CK Kernel <ck@vds.kolivas.org>
Subject: Re: [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling
Date: Wed, 19 Jan 2005 00:54:41 -0600	[thread overview]
Message-ID: <87is5tx61a.fsf@sulphur.joq.us> (raw)
In-Reply-To: <41ED08AB.5060308@kolivas.org> (Con Kolivas's message of "Wed, 19 Jan 2005 00:01:31 +1100")

Con Kolivas <kernel@kolivas.org> writes:

> This patch for 2.6.11-rc1 provides a method of providing real time
> scheduling to unprivileged users which increasingly is desired for
> multimedia workloads.

I ran some jack_test3.2 runs with this, using all the default
settings.  The results of three runs differ quite significantly for no
obvious reason.  I can't figure out why the DSP load should vary so
much.  

These may be bogus results.  It looks like a libjack bug sometimes
causes clients to crash when deactivating.  I will investigate more
tomorrow, and come up with a fix.

For comparison, I also made a couple of runs using the realtime-lsm to
grant SCHED_FIFO privileges.  There was some variablility, but nowhere
near as much (and no crashes).  I used schedtool to verify that the
jackd threads actually have the expected scheduler type.

============================================
Unprivileged, realtime threads are SCHED_ISO
============================================

*** Terminated Tue Jan 18 23:54:55 CST 2005 ***
************* SUMMARY RESULT ****************
Total seconds ran . . . . . . :   300
Number of clients . . . . . . :    20
Ports per client  . . . . . . :     4
Frames per buffer . . . . . . :    64
*********************************************
Timeout Count . . . . . . . . :(    3)          (   14)         (    2)        
XRUN Count  . . . . . . . . . :    10               42               3         
Delay Count (>spare time) . . :     1                0               0         
Delay Count (>1000 usecs) . . :     0                0               0         
Delay Maximum . . . . . . . . : 307419   usecs    6492   usecs   19339   usecs 
Cycle Maximum . . . . . . . . :   858   usecs      866   usecs     860   usecs 
Average DSP Load. . . . . . . :    37.3 %           14.5 %          37.7 %     
Average CPU System Load . . . :    10.2 %            4.5 %          10.0 %     
Average CPU User Load . . . . :    26.6 %           11.4 %          23.8 %     
Average CPU Nice Load . . . . :     0.0 %            0.0 %           0.0 %     
Average CPU I/O Wait Load . . :     2.0 %            0.7 %           0.2 %     
Average CPU IRQ Load  . . . . :     0.8 %            0.7 %           0.7 %     
Average CPU Soft-IRQ Load . . :     0.0 %            0.0 %           0.0 %     
Average Interrupt Rate  . . . :  1730.3 /sec      1695.5 /sec     1694.8 /sec  
Average Context-Switch Rate . : 11523.1 /sec      6151.1 /sec    11672.2 /sec  
*********************************************


==================================================
With CAP_SYS_NICE, realtime threads are SCHED_FIFO
==================================================

*** Terminated Tue Jan 18 23:41:42 CST 2005 ***
************* SUMMARY RESULT ****************
Total seconds ran . . . . . . :   300
Number of clients . . . . . . :    20
Ports per client  . . . . . . :     4
Frames per buffer . . . . . . :    64
*********************************************
Timeout Count . . . . . . . . :(    0)          (    0)        
XRUN Count  . . . . . . . . . :     0                0         
Delay Count (>spare time) . . :     0                0         
Delay Count (>1000 usecs) . . :     0                0         
Delay Maximum . . . . . . . . :   331   usecs      201   usecs 
Cycle Maximum . . . . . . . . :   882   usecs     1017   usecs 
Average DSP Load. . . . . . . :    40.7 %           41.7 %     
Average CPU System Load . . . :    11.1 %           10.9 %     
Average CPU User Load . . . . :    26.7 %           27.7 %     
Average CPU Nice Load . . . . :     0.0 %            0.0 %     
Average CPU I/O Wait Load . . :     0.6 %            1.0 %     
Average CPU IRQ Load  . . . . :     0.7 %            0.7 %     
Average CPU Soft-IRQ Load . . :     0.0 %            0.0 %     
Average Interrupt Rate  . . . :  1708.0 /sec      1697.1 /sec  
Average Context-Switch Rate . : 13297.0 /sec     13314.8 /sec  
*********************************************

-- 
  joq

  parent reply	other threads:[~2005-01-19  6:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 13:01 Con Kolivas
2005-01-18 14:53 ` Con Kolivas
2005-01-18 15:45 ` [ck] " Cal
2005-01-18 15:53   ` Con Kolivas
2005-01-18 16:23     ` Jack O'Quin
2005-01-18 16:17   ` Jack O'Quin
2005-01-19  2:02     ` Lee Revell
2005-01-19  2:08       ` Con Kolivas
2005-01-19  5:26 ` utz
2005-01-19  5:31   ` Con Kolivas
2005-01-19 14:01   ` Con Kolivas
2005-01-19  6:54 ` Jack O'Quin [this message]
2005-01-19  7:56   ` Con Kolivas
2005-01-19 14:27     ` Jack O'Quin
2005-01-19  9:33   ` Con Kolivas
2005-01-19 17:12     ` Jack O'Quin
2005-01-20  0:07       ` Con Kolivas
2005-01-20  1:21         ` Jack O'Quin

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=87is5tx61a.fsf@sulphur.joq.us \
    --to=joq@io.com \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paul@linuxaudiosystems.com \
    --cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome