Sponsored Content
Full Discussion: Real Time processes in Linux
Top Forums UNIX for Advanced & Expert Users Real Time processes in Linux Post 302547331 by kumaran_5555 on Monday 15th of August 2011 08:09:41 AM
Old 08-15-2011
Real Time processes in Linux

I was trying to experiment with SCHED_RR and SCHED_FIFO.

I tried benchmarking the SCHED_NORMAL with these two real time priorities.

What I found is strange result. SHED_RR was the slowest then comes SCHED_FIFO and SCHED_NORMAL was the fastest one.

All tests are run in same situation and independently. And these process are only CPU intensive, no IO.

I expect FIFO to run faster because no no content switching. Can anyone help understand this mystery.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

capturing real time

Newbie question: I wrote korn shell script that lets me connect to a cisco switch thru telnet from sun server. I'm wodering if or what command i would use to capture info that is being sent to standard output when the script is running. Putting part of my script below and results. #!/bin/ksh... (2 Replies)
Discussion started by: wisher115
2 Replies

2. Solaris

Real time problems

Hi friends, I am new to solaris and looking for a job, when ever i attend interview i get most of the questions on real time problems, every one sak me the same questions what are the problems you face daily.. and what are the types? i know few like, disk extension,swap memory increasing,... (2 Replies)
Discussion started by: kurva
2 Replies

3. Programming

problem with real-time

hello every1, i'm very hope so anyone here have experience with lib rt like aio linux based. In first I've a problem with receiving data from aio_buf, i.e. I have received it, but if the next data size less then pervious I've got a noise from a socket. I've tried to fix it by different ways, but... (0 Replies)
Discussion started by: quant
0 Replies

4. Shell Programming and Scripting

Shell script to convert epoch time to real time

Dear experts, I have an epoch time input file such as : - 1302451209564 1302483698948 1302485231072 1302490805383 1302519244700 1302492787481 1302505299145 1302506557022 1302532112140 1302501033105 1302511536485 1302512669550 I need the epoch time above to be converted into real... (4 Replies)
Discussion started by: aismann
4 Replies

5. UNIX for Dummies Questions & Answers

Real time processing

Hi Not sure if this can be achieved by unix , but still would like to know if there is any way by which I can do the below given logic cat sam1 > out1 cat sam2 > out2 when either one of this finished the the next file shd be written in that file, meaning cat sam3 >> out1/out2... (2 Replies)
Discussion started by: Sri3001
2 Replies

6. Shell Programming and Scripting

Converting real time to epoch time

# date +%s -d "Mon Feb 11 02:26:04" 1360567564 # perl -e 'print scalar localtime(1360567564), "\n";' Mon Feb 11 02:26:04 2013 the epoch conversion is working fine. but one of my application needs 13 digit epoch time as input 1359453135154 rather than 10 digit epoch time 1360567564... (3 Replies)
Discussion started by: vivek d r
3 Replies
rtsched(1)						      General Commands Manual							rtsched(1)

NAME
rtsched - execute process/lightweight process (LWP) with real-time priority SYNOPSIS
scheduler priority command [arguments] scheduler] priority scheduler] priority scheduler] priority DESCRIPTION
executes command with POSIX or HP-UX real-time priority, or changes the real-time priority of currently executing process (pid) or light- weight process (lwpid). All POSIX real-time priority processes or LWPs are of greater scheduling importance than processes/LWPs with HP-UX real-time or HP-UX time- share priority. All HP-UX real-time priority processes/LWPs are of greater scheduling importance than HP-UX timeshare priority pro- cesses/LWPs, but are of lesser importance than POSIX real-time processes/LWPs. Neither POSIX nor HP-UX real-time processes/LWPs are subject to degradation. POSIX real-time processes/LWPs may be scheduled with one of three different POSIX real-time schedulers: SCHED_FIFO, SCHED_RR, or SCHED_RR2. See rtsched(2) for details. is a superset of See rtprio(1). Options Specify the desired scheduler: POSIX real-time schedulers: SCHED_FIFO SCHED_RR SCHED_RR2 HP-UX real-time scheduler: SCHED_RTPRIO HP-UX timeshare scheduler: SCHED_HPUX SCHED_NOAGE Specify priority range; any integer within the inclusive priority range of the corresponding scheduler. is required for all schedulers except SCHED_HPUX. If scheduler is SCHED_HPUX, the priority argument is ignored. The default priority range of each scheduler is as follows: scheduler highest priority lowest priority -------------------------------------------------- SCHED_FIFO 31 0 SCHED_RR 31 0 SCHED_RR2 31 0 SCHED_RTPRIO 0 127 SCHED_NOAGE 178 255 SCHED_HPUX N/A N/A Higher numerical values for the priority represent higher priorities under POSIX real-time schedulers, whereas lower numeri- cal values for the priority represent higher priorities under HP-UX real-time and timeshare schedulers. Specify an already executing process ID (pid). Specify an already executing lightweight process ID (lwpid). The target LWP (lwpid) can be in any process. Select all the LWPs in an already executing process (specified with When scheduling policy is not specified explicitly using the option, the process's current schedul- ing policy will be used. If the requested priority value is in the range for this scheduling policy, the scheduling policy and priority of the process and all its LWPs will be changed to these values. Please note that it may cause the scheduling policy to be changed for some LWPs. If the user is not a member of a group having access and is not the user with appropriate privileges, command is not scheduled, or pid's/ lwpid's real-time priority is not changed. When changing the real-time priority of a currently executing process/LWP, the effective user ID of the calling process must be the user with appropriate privileges, or the real or effective user ID must match the real or saved user ID of the process to be modified. In presence of processor sets (see pset_create(2) for details), the application execution is restricted to processors in the application's processor set. The threads in different processor sets do not compete with one another for processors based on their scheduling policy and priority values. The scheduler looks only at threads assigned to a processor's processor set to choose the next thread to run. RETURN VALUE
returns exit status: if command is successfully scheduled or if pid's or lwpid's real-time priority is successfully changed; if command is not executable, pid or lwpid does not exist, or priority is not within the priority range for the corresponding scheduler; if command (pid/lwpid) lacks real-time capability, or the invoker's effective user ID is not a user who has appropriate privi- leges, or the real or effective user or the real or effective user ID does not match the real or saved user ID of the process being changed; or if rtsched encountered an internal error or if rtsched is not supported by this release. EXAMPLES
Execute file with SCHED_FIFO at a priority of 10: Execute file with SCHED_RTPRIO at a priority of 127 (this is synonymous to Execute file with the SCHED_HPUX scheduler: This is useful to spawn a timeshare priority command from a real-time priority shell. Set the currently running process, pid 24217, to execute with SCHED_RR2 at a priority of 20: Now change its priority to 10 using the same scheduler: Set the currently running LWP, lwpid 987312, to execute with SCHED_RR at a priority of 10: Set all currently executing LWPs in a process pid 21342 to execute with SCHED_FIFO at a priority of 25: WARNINGS
The priority values used by may differ from those used by other commands. For example, ps(1) displays the internal representation of pri- ority values. AUTHOR
was developed by HP. SEE ALSO
rtprio(1), setprivgrp(1M), getprivgrp(2), pset_create(2), rtprio(2), rtsched(2), _lwp_getscheduler(2), _lwp_setscheduler(2), pstat_getlwp(2). rtsched(1)
All times are GMT -4. The time now is 03:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy