hi manjunath,
i googled for u............
what i got is ............
Quiescent State:
A point in the code where all of the current CPU's temporary variables that were previously in use in a critical section are dead. In a non-preemptive Linux kernel, a context switch is a quiescent state for CPUs. In a preemptive Linux kernel,
rcu_read_lock() and rcu_read_unlock() suppress preemption for short read-side critical sections, so that context switch is still a quiescent state with respect to these read-side critical sections. Although there are implementations of RCU that do not require preemption to be suppressed [
Gamsa99,
McK02a], they can be prone to excessively long grace periods.
"
www.usenix.org/events/usenix03/tech/freenix03/full_papers/arcangeli/arcangeli_html/node4.html
"
seriously i don't know what it is telling........ if you can understood....correct me
bye
Ashok
On 5/10/06, Manjunath Naik <peter.desouzain@xxxxxxxxx> wrote:
What is quiescent state? I had read some-thing like this in one of the article.
For example, in a non-preemtive kernel, context switch is a quiescent state for given CPU.
Thanks
