| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAGZFCEHb2Cb_LGXtcYmhDvd0d0zjdb3-5D7-6EBjXmHLJESYoA@mail.gmail.com> Date: Wed, 17 Apr 2013 15:35:15 +0530 From: ratheesh kannoth <ratheesh.ksz@...il.com> To: linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org Subject: scheduler context I would like to understand on linux scheduler context. I have read a lot in websites and i could find contradictory statement. There are so many mailing list also ,but with less info. I would really appreciate if anybody could spend some time answering my question. 1. Which context scheduler run ? ( process context or interrupt context ). 2. scheduler is the guy who picks up the next candidate to run. if it gets interrupted by hardirq, what will happen ? 3. if scheduler run in process context , how bottom half are scheduled ? 4. In smp, schedule() function may be called simultaneously. How it is handled ? 5. When a bottom half is interrupted by hard irq, how softirq kernel thread saves the state and restart it later ? ...what i mean is , an hardirq came and its isr executed. bottom half enabled and bottom half gets scheduled . Before bottom half is completed , next irq came and it enables bottom half , and the new bottom half is scheduled ....So here , what will happen to old bottom half , will it again run later ? Thanks, Ratheesh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists