Kent Overstreet <koverstr...@google.com> writes: > This implements a refcount with similar semantics to > atomic_get()/atomic_dec_and_test(), that starts out as just an atomic_t > but dynamically switches to per cpu refcounting when the rate of > gets/puts becomes too high.
This will only work if you put on the same CPU as you get, right? In this case I would rather use RCU. It's clearly unusable for anything blocking (or not get_cpu) Normally RCU already handles the "ref count for short non blocking case" Is that really true for AIO? It seems dubious. -Andi -- a...@linux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
