![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Compiling 32 bit app on 64 bit kernal | morrisey | AIX | 3 | 03-19-2008 03:37 PM |
| Kernal Information | shaan_dmp | UNIX for Dummies Questions & Answers | 4 | 02-15-2007 06:55 AM |
| reload kernal without reboot | dozy | Linux | 3 | 10-02-2005 08:20 AM |
| Kernal Panic | jcoleman544 | UNIX for Dummies Questions & Answers | 3 | 06-09-2003 07:50 AM |
| kernal log message | reddyb | UNIX for Advanced & Expert Users | 1 | 10-29-2001 11:09 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
hello all,
as we know that the kernal Schedules tasks with some time slice given to each. how does the Kernal know that the time of a Task has been elapsed? does it follow the syatem Clock?or how? thanks for your time |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
#3
|
||||
|
||||
|
dsberrf has a valid point, this would be a lengthy chapter in a book. Another point is that different kernels has different algorithms for scheduling. But briefly, the "clock" is a component that generates periodic interrupts. The interrupt routine does stuff when it is called by the clock. A major routine is called a certain number of times per second with 100 times per second being a common value. This major routine is called a "clock tick" (or "jiffy" on linux). A process' timeslice might be one tenth of a second so this would be represented as a 10. The timeslice is always some fixed number of "clock ticks". At each clock tick, it is decremented. When it hits zero, the scheduler will decide which process gets the cpu. If no other process wants the cpu, the process might get another timeslice.
There is a lot more to this, but I'm not going to write that lengthy chapter... |
|
#4
|
||||
|
||||
|
I wasn't trying to be a smart A$$, just so you know.
Also, Perderabo has given one of the best short descriptions I've seen. Which is the main reason I did NOT. [dsbeerf == FreeBSD, backwards.] |
|
#5
|
|||
|
|||
|
I got some Idea and go through the lonk given.
thanks |
|||
| Google The UNIX and Linux Forums |