From: Tejun Heo <tj@kernel.org>
To: Kent Overstreet <koverstreet@google.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-aio@kvack.org, akpm@linux-foundation.org,
Zach Brown <zab@redhat.com>, Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Jens Axboe <axboe@kernel.dk>,
Asai Thambi S P <asamymuthupa@micron.com>,
Selvan Mani <smani@micron.com>,
Sam Bradshaw <sbradshaw@micron.com>,
Jeff Moyer <jmoyer@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>,
Benjamin LaHaise <bcrl@kvack.org>,
Oleg Nesterov <oleg@redhat.com>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 04/21] Generic percpu refcounting
Date: Tue, 14 May 2013 07:59:32 -0700 [thread overview]
Message-ID: <20130514145932.GA6607@mtj.dyndns.org> (raw)
In-Reply-To: <1368494338-7069-5-git-send-email-koverstreet@google.com>
Hello,
On Mon, May 13, 2013 at 06:18:41PM -0700, Kent Overstreet wrote:
> +/**
> + * percpu_ref_dead - check if a dynamic percpu refcount is shutting down
> + *
> + * Returns true if percpu_ref_kill() has been called on @ref, false otherwise.
Explanation on synchronization and use cases would be nice. People
tend to develop massive mis-uses for interfaces like this.
> + */
> +static inline int percpu_ref_dead(struct percpu_ref *ref)
> +{
> + return ref->pcpu_count == NULL;
> +}
...
> +/*
> + * The trick to implementing percpu refcounts is shutdown. We can't detect the
> + * ref hitting 0 on every put - this would require global synchronization and
> + * defeat the whole purpose of using percpu refs.
> + *
> + * What we do is require the user to keep track of the initial refcount; we know
> + * the ref can't hit 0 before the user drops the initial ref, so as long as we
> + * convert to non percpu mode before the initial ref is dropped everything
> + * works.
Can you please also explain why per-cpu wrapping is safe somewhere?
> + * Converting to non percpu mode is done with some RCUish stuff in
> + * percpu_ref_kill. Additionally, we need a bias value so that the atomic_t
> + * can't hit 0 before we've added up all the percpu refs.
> + */
> +
> +#define PCPU_COUNT_BIAS (1ULL << 31)
Are we sure this is enough? 1<<31 is a fairly large number but it's
just easy enough to breach from time to time and it's gonna be hellish
to reproduce / debug when it actually overflows. Maybe we want
atomic64_t w/ 1LLU << 63 bias? Or is there something else which
guarantees that the bias can't over/underflow?
> +int percpu_ref_tryget(struct percpu_ref *ref)
> +{
> + int ret = 1;
> +
> + preempt_disable();
> +
> + if (!percpu_ref_dead(ref))
> + percpu_ref_get(ref);
> + else
> + ret = 0;
> +
> + preempt_enable();
> +
> + return ret;
> +}
Why isn't the above one inline?
Why no /** comment on public functions? It'd be great if you can
explicitly warn about the racy nature of the function - especially,
the function may return overflowed or zero refcnt. BTW, why is this
function necessary? What's the use case?
> +unsigned percpu_ref_count(struct percpu_ref *ref)
> +{
> + unsigned __percpu *pcpu_count;
> + unsigned count = 0;
> + int cpu;
> +
> + preempt_disable();
> +
> + count = atomic_read(&ref->count);
> +
> + pcpu_count = ACCESS_ONCE(ref->pcpu_count);
> +
> + if (pcpu_count)
> + for_each_possible_cpu(cpu)
> + count += *per_cpu_ptr(pcpu_count, cpu);
> +
> + preempt_enable();
> +
> + return count;
> +}
...
> +/**
> + * percpu_ref_kill - prepare a dynamic percpu refcount for teardown
> + *
> + * Must be called before dropping the initial ref, so that percpu_ref_put()
> + * knows to check for the refcount hitting 0. If the refcount was in percpu
> + * mode, converts it back to single atomic counter mode.
> + *
> + * The caller must issue a synchronize_rcu()/call_rcu() before calling
> + * percpu_ref_put() to drop the initial ref.
> + *
> + * Returns true the first time called on @ref and false if @ref is already
> + * shutting down, so it may be used by the caller for synchronizing other parts
> + * of a two stage shutdown.
> + */
I'm not sure I like this interface. Why does it allow being called
multiple times? Why is that necessary? Wouldn't just making it
return void and trigger WARN_ON() if it detects that it's being called
multiple times better? Also, why not bool if the return value is
true/false?
> +int percpu_ref_kill(struct percpu_ref *ref)
> +{
> + unsigned __percpu *pcpu_count;
> + unsigned __percpu *old;
> + unsigned count = 0;
> + int cpu;
> +
> + pcpu_count = ACCESS_ONCE(ref->pcpu_count);
> +
> + do {
> + if (!pcpu_count)
> + return 0;
> +
> + old = pcpu_count;
> + pcpu_count = cmpxchg(&ref->pcpu_count, old, NULL);
> + } while (pcpu_count != old);
> +
> + synchronize_sched();
And this makes the whole function blocking. Why not use call_rcu() so
that the ref can be called w/o sleepable context too?
> +
> + for_each_possible_cpu(cpu)
> + count += *per_cpu_ptr(pcpu_count, cpu);
> +
> + free_percpu(pcpu_count);
> +
> + pr_debug("global %lli pcpu %i",
> + (int64_t) atomic_read(&ref->count), (int) count);
> +
> + atomic_add((int) count - PCPU_COUNT_BIAS, &ref->count);
> +
> + return 1;
> +}
> +
> +/**
> + * percpu_ref_put_initial_ref - safely drop the initial ref
> + *
> + * A percpu refcount needs a shutdown sequence before dropping the initial ref,
> + * to put it back into single atomic_t mode with the appropriate barriers so
> + * that percpu_ref_put() can safely check for it hitting 0 - this does so.
> + *
> + * Returns true if @ref hit 0.
> + */
> +int percpu_ref_put_initial_ref(struct percpu_ref *ref)
> +{
> + if (percpu_ref_kill(ref)) {
> + return percpu_ref_put(ref);
> + } else {
> + WARN_ON(1);
> + return 0;
> + }
> +}
Can we just roll the above into percpu_ref_kill()? It's much harder
to misuse if kill puts the base ref.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-05-14 14:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 1:18 AIO refactoring/performance improvements/cancellation Kent Overstreet
2013-05-14 1:18 ` [PATCH 01/21] aio: fix kioctx not being freed after cancellation at exit time Kent Overstreet
2013-05-14 1:18 ` [PATCH 02/21] aio: reqs_active -> reqs_available Kent Overstreet
2013-05-14 1:18 ` [PATCH 03/21] aio: percpu reqs_available Kent Overstreet
2013-05-14 1:18 ` [PATCH 04/21] Generic percpu refcounting Kent Overstreet
2013-05-14 13:51 ` Oleg Nesterov
2013-05-15 8:21 ` Kent Overstreet
2013-05-14 14:59 ` Tejun Heo [this message]
2013-05-14 15:28 ` Oleg Nesterov
2013-05-15 9:00 ` Kent Overstreet
2013-05-15 8:58 ` Kent Overstreet
2013-05-15 17:37 ` Tejun Heo
2013-05-28 23:47 ` Kent Overstreet
2013-05-29 1:11 ` Tejun Heo
2013-05-29 4:59 ` Rusty Russell
2013-05-31 20:12 ` Kent Overstreet
2013-05-14 21:59 ` Tejun Heo
2013-05-14 22:15 ` Tejun Heo
2013-05-15 9:07 ` Kent Overstreet
2013-05-15 17:56 ` Tejun Heo
2013-05-16 0:26 ` Rusty Russell
2013-05-14 1:18 ` [PATCH 05/21] aio: percpu ioctx refcount Kent Overstreet
2013-05-14 1:18 ` [PATCH 06/21] aio: io_cancel() no longer returns the io_event Kent Overstreet
2013-05-14 1:18 ` [PATCH 07/21] aio: Don't use ctx->tail unnecessarily Kent Overstreet
2013-05-14 1:18 ` [PATCH 08/21] aio: Kill aio_rw_vect_retry() Kent Overstreet
2013-05-14 1:18 ` [PATCH 09/21] aio: Kill unneeded kiocb members Kent Overstreet
2013-05-14 1:18 ` [PATCH 10/21] aio: Kill ki_users Kent Overstreet
2013-05-14 1:18 ` [PATCH 11/21] aio: Kill ki_dtor Kent Overstreet
2013-05-14 1:18 ` [PATCH 12/21] aio: convert the ioctx list to radix tree Kent Overstreet
2013-05-14 1:18 ` [PATCH 13/21] block: prep work for batch completion Kent Overstreet
2013-05-14 1:18 ` [PATCH 14/21] block, aio: batch completion for bios/kiocbs Kent Overstreet
2013-05-14 1:18 ` [PATCH 15/21] virtio-blk: convert to batch completion Kent Overstreet
2013-05-14 1:18 ` [PATCH 16/21] mtip32xx: " Kent Overstreet
2013-05-14 1:18 ` [PATCH 17/21] Percpu tag allocator Kent Overstreet
2013-05-14 13:48 ` Oleg Nesterov
2013-05-14 14:24 ` Oleg Nesterov
2013-05-15 9:34 ` Kent Overstreet
2013-05-15 9:25 ` Kent Overstreet
2013-05-15 15:41 ` Oleg Nesterov
2013-05-15 16:10 ` Oleg Nesterov
2013-06-10 23:20 ` Kent Overstreet
2013-06-11 17:42 ` Oleg Nesterov
2013-05-14 15:03 ` Tejun Heo
2013-05-15 20:19 ` Andi Kleen
2013-05-14 1:18 ` [PATCH 18/21] aio: Allow cancellation without a cancel callback, new kiocb lookup Kent Overstreet
2013-05-14 1:18 ` [PATCH 19/21] aio/usb: Update cancellation for new synchonization Kent Overstreet
2013-05-14 1:18 ` [PATCH 20/21] direct-io: Set dio->io_error directly Kent Overstreet
2013-05-14 1:18 ` [PATCH 21/21] block: Bio cancellation Kent Overstreet
2013-05-15 17:52 ` Jens Axboe
2013-05-15 19:29 ` Kent Overstreet
2013-05-15 20:01 ` Jens Axboe
2013-05-31 22:52 ` Kent Overstreet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130514145932.GA6607@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=asamymuthupa@micron.com \
--cc=axboe@kernel.dk \
--cc=balbi@ti.com \
--cc=bcrl@kvack.org \
--cc=cl@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlbec@evilplan.org \
--cc=jmoyer@redhat.com \
--cc=koverstreet@google.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=sbradshaw@micron.com \
--cc=smani@micron.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zab@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®