• J
    fsnotify: destroy marks with call_srcu instead of dedicated thread · c510eff6
    Jeff Layton 提交于
    At the time that this code was originally written, call_srcu didn't
    exist, so this thread was required to ensure that we waited for that
    SRCU grace period to settle before finally freeing the object.
    
    It does exist now however and we can much more efficiently use call_srcu
    to handle this.  That also allows us to potentially use srcu_barrier to
    ensure that they are all of the callbacks have run before proceeding.
    In order to conserve space, we union the rcu_head with the g_list.
    
    This will be necessary for nfsd which will allocate marks from a
    dedicated slabcache.  We have to be able to ensure that all of the
    objects are destroyed before destroying the cache.  That's fairly
    Signed-off-by: NJeff Layton <jeff.layton@primarydata.com>
    Cc: Eric Paris <eparis@parisplace.org>
    Reviewed-by: NJan Kara <jack@suse.com>
    Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
    Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
    Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
    c510eff6
fsnotify_backend.h 16.8 KB