All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: joonas.lahtinen@linux.intel.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: Mon, 01 May 2017 11:05:28 +0900	[thread overview]
Message-ID: <16988.1493604328@jrobl> (raw)
In-Reply-To: <20170430094348.GA5970@redhat.com>

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.

It was a few weeks ago when you posted. It is a pity the fix was not
merged before v4.11 comes out. I know v4.11 will appear soon. So I'd ask
i915 developers, would you test Andrea Arcangeli's fix and release it as
v4.11.1 as soon as possible?


J. R. Okajima

  reply	other threads:[~2017-05-01  2:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30  6:07 Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers J. R. Okajima
2017-04-30  9:43 ` Andrea Arcangeli
2017-05-01  2:05   ` J. R. Okajima [this message]
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
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=16988.1493604328@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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 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.