From: Andrea Arcangeli <aarcange@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"J. R. Okajima" <hooanon05g@gmail.com>,
chris@chris-wilson.co.uk, daniel.vetter@ffwll.ch,
jani.nikula@intel.com, linux-kernel@vger.kernel.org
Subject: Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers
Date: Wed, 10 May 2017 12:43:54 +0200 [thread overview]
Message-ID: <20170510104354.GB5011@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1705091952090.3043@eggly.anvils>
Hello,
On Tue, May 09, 2017 at 08:04:24PM -0700, Hugh Dickins wrote:
> On Mon, 8 May 2017, Joonas Lahtinen wrote:
> > On pe, 2017-05-05 at 14:57 -0700, Hugh Dickins wrote:
> > > On Fri, 5 May 2017, Joonas Lahtinen wrote:
> > > > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > > > > Thanx for the reply.
> > > > >
> > > > > Andrea Arcangeli:
> > > > > >
> > > > > > Yes I already reported this, my original fix was way more efficient
> > > > > > (and also safer considering the above) than what landed upstream. My
> > > > > > feedback was ignored though.
> > > > > >
> > > > > > https://lists.freedesktop.org/archives/intel-gfx/2017-April/125414.html
> > > > >
> > > > > I see.
> > > > > Actually on my test system for v4.11-rc8, kthreadd, kworker, kswapd and
> > > > > others all stopped working due to the synchronize_rcu_expedited call
> > > > > from i915_gem_shrinker_count. It is definitly a show stopper for me as
> > > > > an i915 user.
> > > >
> > > > Filing a bug in freedesktop.org with all the details is the fastest way
> > > > of getting help. Without the bug (and with such little information as
> > > > the previous e-mail) it's hard to estimate the extent and nature of the
> > > > bug.
> > > >
> > > > I've anyway gone and prepared a patch to drop the RCU sync completely
> > > > from shrinker phase, as discussed originally with Chris.
> > >
> > > Is that a patch that will be suitable for 4.11-stable? Please do post
> > > it here. I had not experienced this i915-induced hang at all when
> > > Andrea first mentioned it, nor even on 4.11-rc8; but now with 4.11
> > > final I can get it fairly easily (I haven't tried Andrea's fix yet).
> >
> > Please try:
> >
> > https://patchwork.freedesktop.org/patch/154713/
> >
> > If it works, a Tested-by: would be appreciated.
>
> Yes, that works for me, thank you.
>
> Tested-by: Hugh Dickins <hughd@google.com>
>
> But the linked patch seems to be lacking a Reported-by (not me) tag,
> a Fixes tag, a Cc stable tag, and any indication in the Subject or
> commit message that this patch is something needed to fix hangs
> observed by several people - it just sounds like a minor cleanup.
It works for me too. I'm running my workstation also with
synchronize_rcu removed from i915_gem_shrink_all in addition to the
above. Isn't the oom method invoked from reclaim context too? As far
as I can tell synchronize_rcu can end up throttling on a background
synchronize_rcu_expedited(), so it might end up in the same issue
unless removed too.
Tested-by: Andrea Arcangeli <aarcange@redhat.com>
(I can't reproduce the lockups 100% of the time, but they never
happened again with this patch and I happened to run the load that
reproduces them a couple of times already with v4.11 and this patch
applied)
It's also certainly improving performance by removing the
synchronize_rcu_expedited from the _count methods where it was useless
(in addition to unsafe).
Thanks,
Andrea
next prev parent reply other threads:[~2017-05-10 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 6:07 J. R. Okajima
2017-04-30 9:43 ` Andrea Arcangeli
2017-05-01 2:05 ` J. R. Okajima
2017-05-05 9:39 ` Joonas Lahtinen
2017-05-05 21:57 ` Hugh Dickins
2017-05-08 8:04 ` Joonas Lahtinen
2017-05-10 3:04 ` Hugh Dickins
2017-05-10 9:54 ` Joonas Lahtinen
2017-05-10 10:43 ` Andrea Arcangeli [this message]
2017-05-10 11:01 ` Joonas Lahtinen
2017-05-05 23:28 ` J. R. Okajima
2017-05-20 1:56 ` J. R. Okajima
2017-05-22 6:02 ` Joonas Lahtinen
2017-05-30 20:00 ` Hugh Dickins
2017-05-31 7:10 ` Jani Nikula
2017-05-31 7:27 ` Joonas Lahtinen
2017-06-14 23:05 ` J. R. Okajima
2017-06-15 7:07 ` Jani Nikula
2017-06-26 23:15 ` J. R. Okajima
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=20170510104354.GB5011@redhat.com \
--to=aarcange@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=hooanon05g@gmail.com \
--cc=hughd@google.com \
--cc=jani.nikula@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome