On Tue, Jun 17, 2014 at 09:07:59PM -0400, Tejun Heo wrote: > Hello, > > Currently, percpu_ref destruction - freeing the percpu counter - > happens when the percpu_ref is released. This while a bit more > convenient restricts how percpu_ref can be used. It can't be > initialized with static percpu area and it can't be reinitialized > without going through percpu allocation. > > There are use cases which can take advantage of cycling percpu_ref > through init/release multiple times. This patchset separates out > percpu_ref destruction into percpu_exit() which should be invoked > explicitly and introduces percpu_ref_reinit() which can be used to > recycle a released percpu_ref. > > This patchset doesn't add any users. Patchset to use this will soon > be posted. > > This patchset contains the following six patches. > > 0001-percpu-refcount-aio-use-percpu_ref_cancel_init-in-io.patch > 0002-percpu-refcount-one-bit-is-enough-for-REF_STATUS.patch > 0003-percpu-refcount-add-helpers-for-percpu_count-accesse.patch > 0004-percpu-refcount-use-unsigned-long-for-pcpu_count-poi.patch > 0005-percpu-refcount-require-percpu_ref-to-be-exited-expl.patch > 0006-percpu-refcount-implement-percpu_ref_reinit-and-perc.patch
Applied to percpu/for-3.17. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
