From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Goel, Akash" <akash.goel@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, Sourab Gupta <sourab.gupta@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: Make pages of GFX allocations movable
Date: Thu, 24 Mar 2016 08:13:08 +0000 [thread overview]
Message-ID: <20160324081308.GA26929@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <56F252EA.1020600@intel.com>
On Wed, Mar 23, 2016 at 01:55:14PM +0530, Goel, Akash wrote:
>
>
> On 3/23/2016 1:28 PM, Chris Wilson wrote:
> >On Wed, Mar 23, 2016 at 11:39:44AM +0530, akash.goel@intel.com wrote:
> >>+#ifdef CONFIG_MIGRATION
> >>+static int i915_migratepage(struct address_space *mapping,
> >>+ struct page *newpage, struct page *page,
> >>+ enum migrate_mode mode, void *dev_priv_data)
> >
> >If we move this to i915_gem_shrink_migratepage (i.e. i915_gem_shrink),
> >we can
> >
> >>+ /*
> >>+ * Use trylock here, with a timeout, for struct_mutex as
> >>+ * otherwise there is a possibility of deadlock due to lock
> >>+ * inversion. This path, which tries to migrate a particular
> >>+ * page after locking that page, can race with a path which
> >>+ * truncate/purge pages of the corresponding object (after
> >>+ * acquiring struct_mutex). Since page truncation will also
> >>+ * try to lock the page, a scenario of deadlock can arise.
> >>+ */
> >>+ while (!mutex_trylock(&dev->struct_mutex) && --timeout)
> >>+ schedule_timeout_killable(1);
> >
> >replace this with i915_gem_shrinker_lock() and like constructs with the
> >other shrinkers.
>
> fine, will rename the function to gem_shrink_migratepage, move it
> inside the gem_shrinker.c file, and use the existing constructs.
>
> > Any reason for dropping the early
> > if (!page_private(obj)) skip?
> >
>
> Would this sequence be fine ?
>
> if (!page_private(page))
> goto migrate; /*skip */
>
> Loop for locking mutex
>
> obj = (struct drm_i915_gem_object *)page_private(page);
>
> if (!PageSwapCache(page) && obj) {
Yes.
> >Similarly there are other patterns here that would benefit from
> >integration with existing shrinker logic. However, things like tidying
> >up the pin_display, unbinding, rpm lock inversion are still only on
> >list.
>
> Tidying, like split that one single if condition into multiple if,
> else if blocks ?
Just outstanding patches that simplify the condition and work we have to
do here.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
--
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-03-24 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 6:09 [PATCH 1/2] shmem: Support for registration of Driver/file owner specific ops akash.goel
2016-03-23 6:09 ` [PATCH 2/2] drm/i915: Make pages of GFX allocations movable akash.goel
2016-03-23 7:58 ` Chris Wilson
2016-03-23 8:25 ` Goel, Akash
2016-03-24 8:13 ` Chris Wilson [this message]
2016-03-24 18:22 ` [PATCH v2 " akash.goel
2016-03-24 18:40 ` Chris Wilson
2016-04-04 11:27 ` [PATCH v3 " akash.goel
2016-03-24 12:11 ` [Intel-gfx] [PATCH 1/2] shmem: Support for registration of Driver/file owner specific ops Joonas Lahtinen
2016-10-19 15:11 ` akash goel
2016-10-20 15:15 ` Joonas Lahtinen
2016-11-04 12:48 ` [PATCH 1/2] shmem: Support for registration of driver/file " akash.goel
2016-11-04 12:48 ` [PATCH 2/2] drm/i915: Make GPU pages movable akash.goel
2016-11-04 13:37 ` Chris Wilson
2016-11-04 13:53 ` Goel, Akash
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=20160324081308.GA26929@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=akash.goel@intel.com \
--cc=hughd@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--cc=sourab.gupta@intel.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