lkml.org 
[lkml]   [2005]   [Apr]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
    Date
    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()
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2005-04-06 13:31    [W:2.995 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site