prasanna wakhare (prasannawakhare@xxxxxxxxx) wrote: > Hi, > Some facts about timer handler: > When Scheduler invokes in 2.4? At every timer > interrupt jiffies are incremented and check is made > if current process time slice is over or it is waiting > for I/O ,so if its need_resched flag is set the > scheduler is invoked. > After this moment, > In case of code interrupt by a timer handler, at > IRET(interrupt return) the check is made whether the > code interrupted belongs to user land or kernel mode , > If the code belongs to user land scheduler is invoked > immediately, if code is of kernel mode the interrupted > path is resume without invoking scheduler. > Please forgive me if i was wrong B'coz i think > something i missed out. > Prasanna. I think you would say : user context and not userland ?? Because of : - userland is in ring 3 - user context is in ring 0 (from a syscall from userland) Have a good day. -- Amicalement/Regards Christophe ----------------------------------------------------------------- Christophe Lucas <c.lucas@xxxxxxxxxxx> developer/sysadmin Registered User #271267 http://odie.mcom.fr/~clucas/ RotomaLUG member (http://www.rotomalug.org) gpg dsa: 0x1E87C874 ----------------------------------------------------------------- Si tu invites des gens qui ont tous le même groupe sanguin à une fête, mais que tu le leur dis pas, ils vont parler d'autre chose. -- J.C. VanDamme
Attachment:
signature.asc
Description: Digital signature
