From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/6] drm/i915: Split the batch pool by engine
Date: Wed, 18 Mar 2015 17:33:49 +0000 [thread overview]
Message-ID: <5509B6FD.60903@linux.intel.com> (raw)
In-Reply-To: <20150318172747.GG10812@nuc-i3427.alporthouse.com>
On 03/18/2015 05:27 PM, Chris Wilson wrote:
> On Wed, Mar 18, 2015 at 04:51:58PM +0000, Tvrtko Ursulin wrote:
>> On 03/09/2015 09:55 AM, Chris Wilson wrote:
>>> diff --git a/drivers/gpu/drm/i915/i915_gem_batch_pool.c b/drivers/gpu/drm/i915/i915_gem_batch_pool.c
>>> index 21f3356cc0ab..1287abf55b84 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem_batch_pool.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem_batch_pool.c
>>> @@ -96,8 +96,9 @@ i915_gem_batch_pool_get(struct i915_gem_batch_pool *pool,
>>>
>>> list_for_each_entry_safe(tmp, next,
>>> &pool->cache_list, batch_pool_list) {
>>> + /* The batches are strictly LRU ordered */
>>> if (tmp->active)
>>> - continue;
>>> + break;
>>
>> This hunk would be a better fit for 2/6, correct?
>
> No. The explanation is given by the comment + changelog.
I don't see this patch introducing this strict LRU ordering, rather it
was there before this patch. Am I missing something? If I am not, then I
see this hunk as a better fit with "Tidy batch pool logic", than "Split
the batch pool by engine".
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-18 17:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 9:55 [PATCH 1/6] drm/i915: Split i915_gem_batch_pool into its own header Chris Wilson
2015-03-09 9:55 ` [PATCH 2/6] drm/i915: Tidy batch pool logic Chris Wilson
2015-03-17 17:42 ` Tvrtko Ursulin
2015-03-17 20:53 ` Chris Wilson
2015-03-09 9:55 ` [PATCH 3/6] drm/i915: Split the batch pool by engine Chris Wilson
2015-03-18 16:51 ` Tvrtko Ursulin
2015-03-18 17:27 ` Chris Wilson
2015-03-18 17:33 ` Tvrtko Ursulin [this message]
2015-03-19 9:36 ` Tvrtko Ursulin
2015-03-19 10:06 ` Chris Wilson
2015-03-19 11:39 ` Tvrtko Ursulin
2015-03-19 11:46 ` Chris Wilson
2015-03-19 11:58 ` Tvrtko Ursulin
2015-03-19 12:04 ` Chris Wilson
2015-03-19 14:01 ` Tvrtko Ursulin
2015-03-19 14:34 ` Chris Wilson
2015-03-09 9:55 ` [PATCH 4/6] drm/i915: Free batch pool when idle Chris Wilson
2015-03-19 17:03 ` Tvrtko Ursulin
2015-03-19 17:14 ` Chris Wilson
2015-03-19 17:27 ` Tvrtko Ursulin
2015-03-09 9:55 ` [PATCH 5/6] drm/i915: Split batch pool into size buckets Chris Wilson
2015-03-19 17:35 ` Tvrtko Ursulin
2015-03-19 21:09 ` Chris Wilson
2015-03-20 9:25 ` Tvrtko Ursulin
2015-03-09 9:55 ` [PATCH 6/6] drm/i915: Include active flag when describing objects in debugfs Chris Wilson
2015-03-09 14:59 ` shuang.he
2015-03-19 17:41 ` Tvrtko Ursulin
2015-03-19 21:05 ` Chris Wilson
2015-03-20 9:23 ` Tvrtko Ursulin
2015-03-19 17:37 ` [PATCH 1/6] drm/i915: Split i915_gem_batch_pool into its own header Tvrtko Ursulin
2015-03-19 21:06 ` Chris Wilson
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=5509B6FD.60903@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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