From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: linux-kernel@vger.kernel.org, keithp@keithp.com,
airlied@linux.ie, dri-devel@lists.freedesktop.org
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: [PATCH] i915: slab shrinker have to return -1 if it can't shrink any objects
Date: Fri, 24 Jun 2011 17:03:22 +0900 [thread overview]
Message-ID: <4E0444CA.3080407@jp.fujitsu.com> (raw)
Now, i915_gem_inactive_shrink() should return -1 instead of 0 if it
can't take a lock. Otherwise, vmscan is getting a lot of confusing
because vmscan can't distinguish "can't take a lock temporary" and
"we've shrank all of i915 objects".
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Keith Packard <keithp@keithp.com>
Cc: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org
---
I've found this issue by reviewing. I hope i915 developers confirm this.
Thx.
drivers/gpu/drm/i915/i915_gem.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 94c84d7..2f9a9b2 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -4104,7 +4104,7 @@ i915_gem_inactive_shrink(struct shrinker *shrinker, struct shrink_control *sc)
int cnt;
if (!mutex_trylock(&dev->struct_mutex))
- return 0;
+ return nr_to_scan ? -1 : 0;
/* "fast-path" to count number of available objects */
if (nr_to_scan == 0) {
--
1.7.3.1
next reply other threads:[~2011-06-24 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 8:03 KOSAKI Motohiro [this message]
2011-06-30 3:53 ` [PATCH] i915: slab shrinker have to return -1 if it can't shrink any objects Keith Packard
2011-06-30 8:55 ` [PATCH] i915: slab shrinker have to return -1 if it cant " Chris Wilson
2011-07-12 9:36 ` KOSAKI Motohiro
2011-07-12 10:06 ` Chris Wilson
2011-07-13 0:19 ` KOSAKI Motohiro
2011-07-13 7:41 ` Chris Wilson
2011-07-13 8:19 ` KOSAKI Motohiro
2011-07-13 8:40 ` Chris Wilson
2011-07-13 11:34 ` Dave Chinner
2011-07-13 10:42 ` Dave Chinner
2011-07-14 2:48 ` KOSAKI Motohiro
2011-07-14 3:47 ` Dave Chinner
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=4E0444CA.3080407@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.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