Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24365 - [boinc] 6.10.58-1 processes seem to run in real time
Attached to Project:
Community Packages
Opened by Daniel Hill (YellowOnion) - Saturday, 21 May 2011, 06:07 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Tuesday, 13 March 2012, 18:28 GMT
Opened by Daniel Hill (YellowOnion) - Saturday, 21 May 2011, 06:07 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Tuesday, 13 March 2012, 18:28 GMT
|
DetailsDescription:
boinc and boinc-nox processes are running in real time Additional info: appending --no_priority_change to boinc_client fixes this, but probably want something like a ulimit/limits.conf (couldn't figure this one out) to enforce/disable real time Steps to reproduce: $ ps -eo pid,rtprio,nice,cmd | grep planck 16396 0 - ../../projects/aqua.dwavesys.com/fokker_planck_2.10_x86_64-pc-linux-gnu__fpmt --T 0.003 --t_f 0.001 --n_particles_per 2 --h_ramp_mid 0.000 --h_ramp_width 0.0005 --time_step_factor 48.0 --gamma_frac 1.0 --t_fraci 0.38 --t_fracf 0.88 --input_file instance.txt_fp_16may11_am_16_003_1000_000-1_126 --nthreads 6 |
This task depends upon
Closed by Jaroslav Lichtblau (Dragonlord)
Tuesday, 13 March 2012, 18:28 GMT
Reason for closing: Not a bug
Tuesday, 13 March 2012, 18:28 GMT
Reason for closing: Not a bug
also the real time kernel is a specialised real time kernel designed with real time in mind, the standard kernel has real time functions but less fine tuning and works perfectly fine in real time mode, I have run JACKd, both ps and JACKd report that they're using real time priority and with a latency of 1.5ms it doesn't stutter while I'm running boinc with nice -19, there's no possibility that JACKd could run with this kind of low latency without real time
even if I was using the real time kernel it shouldn't use real time