From: Peter Zijlstra <peterz@infradead.org>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, Linux MM <linux-mm@kvack.org>,
Jens Axboe <jens.axboe@oracle.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux-foundation.org>,
Hugh Dickins <hugh@veritas.com>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [Intel-gfx] [PATCH v2 1/3] drm/i915: Enable lockless lookup of request tracking via RCU
Date: Tue, 5 Jan 2016 16:06:48 +0100 [thread overview]
Message-ID: <20160105150648.GT6373@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160105150213.GP6344@twins.programming.kicks-ass.net>
On Tue, Jan 05, 2016 at 04:02:13PM +0100, Peter Zijlstra wrote:
> > Shouldn't the slab subsystem do this for us if we request it delays the
> > actual kfree? Seems like a core bug to me ... Adding more folks.
>
> note that sync_rcu() can take a terribly long time.. but yes, I seem to
> remember Paul talking about adding this to reclaim paths for just this
> reason. Not sure that ever happened thouhg.
Also, you might be wanting rcu_barrier() instead, that not only waits
for a GP to complete, but also for all pending callbacks to be
processed.
Without the latter there might still not be anything to free after it.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-05 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 11:19 [PATCH] RFC drm/i915: Remove (struct_mutex) locking for wait-ioctl Chris Wilson
2015-12-23 11:32 ` Chris Wilson
2015-12-23 12:05 ` Chris Wilson
2015-12-23 12:13 ` Chris Wilson
2015-12-23 12:26 ` Chris Wilson
2015-12-23 13:35 ` [PATCH v2 1/3] drm/i915: Enable lockless lookup of request tracking via RCU Chris Wilson
2015-12-23 13:35 ` [PATCH v2 2/3] drm/i915: Remove (struct_mutex) locking for wait-ioctl Chris Wilson
2015-12-23 13:35 ` [PATCH v2 3/3] drm/i915: Remove (struct_mutex) locking for busy-ioctl Chris Wilson
2016-01-05 14:59 ` [Intel-gfx] [PATCH v2 1/3] drm/i915: Enable lockless lookup of request tracking via RCU Daniel Vetter
2016-01-05 15:02 ` Peter Zijlstra
2016-01-05 15:06 ` Peter Zijlstra [this message]
2016-01-05 16:35 ` Paul E. McKenney
2016-01-06 8:06 ` Daniel Vetter
2016-01-06 8:06 ` [Intel-gfx] " Daniel Vetter
2016-01-06 8:38 ` Peter Zijlstra
2016-01-06 8:38 ` [Intel-gfx] " Peter Zijlstra
2016-01-06 15:56 ` Paul E. McKenney
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=20160105150648.GT6373@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chris@chris-wilson.co.uk \
--cc=cl@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jens.axboe@oracle.com \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.