Hi Paul, I'm not quite clear on the difference between the two synchronize functions , the comment for synchronize_sched() seems to have a bit missing? (see below) cheers On Sun, 3 Apr 2005 16:21, Paul E. McKenney wrote: > +/** > + * synchronize_sched - block until all CPUs have exited any non-preemptive > + * kernel code sequences. > + * > + * This means that all preempt_disable code sequences, including NMI and > + * hardware-interrupt handlers, in progress on entry will have completed > + * before this primitive returns. However, this does not guarantee that > + * softirq handlers will have completed, since in some kernels ?? > + * > + * This primitive provides the guarantees made by the (deprecated) > + * synchronize_kernel() API. In contrast, synchronize_rcu() only > + * guarantees that rcu_read_lock() sections will have completed. > + */ > +#define synchronize_sched() synchronize_rcu()
Attachment:
pgplhPxaxqbvW.pgp
Description: PGP signature
- Follow-Ups:
- Re: [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
- From: "Paul E. McKenney" <[email protected]>
- Re: [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
- References:
- [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
- From: "Paul E. McKenney" <[email protected]>
- [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
- Prev by Date: Re: [patch] sched: auto-tune migration costs [was: Re: Industry db benchmark result on recent 2.6 kernels]
- Next by Date: Re: [patch] sched: auto-tune migration costs [was: Re: Industry db benchmark result on recent 2.6 kernels]
- Previous by thread: Re: [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
- Next by thread: Re: [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
- Index(es):
 |