From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Andrea Arcangeli <aarcange@redhat.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: Sat, 20 May 2017 10:56:25 +0900 [thread overview]
Message-ID: <4234.1495245385@jrobl> (raw)
In-Reply-To: <17413.1494026939@jrobl>
"J. R. Okajima":
> I don't know whether the fix is good to me or not yet. I will test your
> fix, but I am busy now and my test will be a few weeks later. Other
> people may want the fix soon. So I'd suggest you to reproduce the
> problem on your side. I guess "mem=1G" or "mem=512M" will make it easier
> to reproduce the problem.
> Of course, if you are sure the fix is correct, then you don't have to
> wait for my test. Release it soon for other people.
Now I am going to able to run my local test.
But V3 patch failed to apply onto v4.11.0.
Would you provide us two versions of the patch, one for v4.11 series and
the other of v4.12-rcN?
J. R. Okajima
next prev parent reply other threads:[~2017-05-20 1:56 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
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 [this message]
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=4234.1495245385@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).