Re: [Jackit-devel] help with realtime capabilities and 2.6.20 kernels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 10, 2007 at 08:16:52PM +0100, Marcos Guglielmetti wrote:
> El Sáb 06 Ene 2007 21:45, Lee Revell escribió:
> > On Sat, 2007-01-06 at 16:21 +0100, Marcos Guglielmetti wrote:
> > > El Vie 05 Ene 2007 05:06, Lee Revell escribió:
> > > > On Thu, 2007-01-04 at 21:47 +0100, Marcos Guglielmetti wrote:
> > > > >  /etc/security/limits.conf
> > > > >
> > > > > @audio     -    rt_priority   100
> > > > > @audio     -    nice      -10
> > > > > @audio     -    memlock     4000000
> > > >
> > > > You might need to use "rtprio" - I don't remember the exact syntax.
> > > >
> > > > Lee
> > >
> > > You are maybe right, but here rtprio did not solved the problem:
> > >
> > > # Testing:
> > > #See page http://mzilikazi.sexypenguins.com/. There that same is
> > > @audio         -     rtprio         99
> > > @audio         -     nice         -10
> > > @audio         -     memlock     250000
> >
> > This is what I have:
> >
> > *               hard    rtprio  99
> > *               hard    nice    -20
> > *               soft    nice    -20
> > *               hard    memlock 500000
> >
> >
> > Works perfectly with PAM version:
> >
> > ii  libpam-modules 0.79-3ubuntu14 Pluggable Authentication Modules for
> > PAM
> >
> > If it does not work for you there must be a bug in the Debian PAM
> > package.
> >
> > Lee
> 
> I copied your config
> 
> > *               hard    rtprio  99
> > *               hard    nice    -20
> > *               soft    nice    -20
> > *               hard    memlock 500000
> 
> 
> to my system, and I am still having the same xruns problems with non-root 
> users, maybe there is a problem with the PAM version into Debian
> 

You mentioned you are still getting xruns ... but have you confirmed if thread
scheduling priority was changed (with the realtime support)?

Here is a quick summary of how I know to check this out:


Three groups of thread scheduling classes
 - SCHED_FIFO , gets high priority and runs until done
 - SCHED_RR , get put in a pool and given run time in a round-robbing fassion
 - SCHED_OTHER, gets least priority

man 2 sched_setscheduler has more details on this.

Threads can also have a numeric priority value from 0 (lowest) to 99 (highest
priority) .

One can see threads with
    ps axm 
    27758 ?        -      0:00 /usr/bin/jackd -T -ndefault --realtime --temporary --driver alsa --rate 48000
        - -        SLs    0:00 -
        - -        SLs    0:00 -
        - -        SLs    0:00 -
        - -        SLs    0:00 -
        - -        SLs    0:00 -


One can see thread SPID with
    ps axm -T
    27758     - ?        -      0:00 /usr/bin/jackd -T -ndefault --realtime --temporary --driver alsa --rate 48000
        - 27758 -        SLs    0:00 -
        - 27759 -        SLs    0:00 -
        - 27760 -        SLs    0:00 -
        - 27761 -        SLs    0:00 -
        - 27762 -        SLs    0:00 -


Or simply with 
    ps ax -T

Another way to view this info is with
    ps -C jackd -cmL

Once the SPID has been observed, the "chrt" (from the "schedutils" debian
package) command can be used to query the thread and see it's priority
    [grauf@grauf grauf]$ ps -C jackd -cmL
      PID   LWP CLS PRI TTY          TIME CMD
    27758     - -     - ?        00:00:39 jackd
        - 27758 TS   16 -        00:00:00 -
        - 27759 TS   17 -        00:00:00 -
        - 27760 TS   24 -        00:00:00 -
        - 27761 FF   60 -        00:00:00 -
        - 27762 FF   50 -        00:00:39 -
    [grauf@grauf grauf]$ chrt -p 27758
    pid 27758's current scheduling policy: SCHED_OTHER
    pid 27758's current scheduling priority: 0
    [grauf@grauf grauf]$ chrt -p 27759
    pid 27759's current scheduling policy: SCHED_OTHER
    pid 27759's current scheduling priority: 0
    [grauf@grauf grauf]$ chrt -p 27760
    pid 27760's current scheduling policy: SCHED_OTHER
    pid 27760's current scheduling priority: 0
    [grauf@grauf grauf]$ chrt -p 27761
    pid 27761's current scheduling policy: SCHED_FIFO
    pid 27761's current scheduling priority: 20
    [grauf@grauf grauf]$ chrt -p 27762
    pid 27762's current scheduling policy: SCHED_FIFO
    pid 27762's current scheduling priority: 10


best luck to you,
donfede

-- 
Federico Grau
Free Software Developer and Sysadmin
Radio Free Asia
2025 M Street, NW
Suite 300
Washington, DC  20036
202-587-2046  Telephone
202-721-7468  Facsimile
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and may
contain information that is privileged and confidential.  Any unauthorized
dissemination, distribution, or copying is strictly prohibited.  If you
receive this transmission in error, please contact network@xxxxxxxx

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user


[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux