All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael H. Nguyen" <michael.h.nguyen@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 0/7] Command parser batch buffer copy
Date: Mon, 01 Dec 2014 14:39:51 -0800	[thread overview]
Message-ID: <547CEE37.40606@intel.com> (raw)
In-Reply-To: <20141127074419.GG10194@nuc-i3427.alporthouse.com>



On 11/26/2014 11:44 PM, Chris Wilson wrote:
> On Wed, Nov 26, 2014 at 01:53:34PM -0800, michael.h.nguyen@intel.com wrote:
>> From: "Michael H. Nguyen" <michael.h.nguyen@intel.com>
>>
>> This is v5 of the series sent here:
>> http://lists.freedesktop.org/archives/intel-gfx/2014-November/055141.html
>>
>> This version incorporates the following feedback from v4.
>>
>> - 0/7 Move 'pending_read_domains |= I915_GEM_DOMAIN_COMMAND' after the
>>    parser (danvet)
>> - 1/7 Move purged check inside the loop (danvet)
>> - 6/7 Move 'shadow_batch_obj->madv = I915_MADV_WILLNEED' inside _get
>>    fnc (danvet)
>> - 7/7 Move pin/unpin calls inside i915_parse_cmds() (Chris W)
>>
>> Issue: VIZ-4719
>> Brad Volkin (7):
>>    drm/i915: Implement a framework for batch buffer pools
>>    drm/i915: Use batch pools with the command parser
>>    drm/i915: Add a batch pool debugfs file
>>    drm/i915: Add batch pool details to i915_gem_objects debugfs
>>    drm/i915: Use batch length instead of object size in command parser
>>    drm/i915: Mark shadow batch buffers as purgeable
>>    drm/i915: Tidy up execbuffer command parsing code
>
> This still does not incorporate the feedback from the last N cycles.
>
> Chiefly: A single cache list, madvise on creation, and squash the
> framework and debugging patches into one.

Re: single cache list

OK. Found the feedback in an old rev.

Re: madvise on creation

Were you referring to this?

from 
http://lists.freedesktop.org/archives/intel-gfx/2014-November/055060.htm

	obj = i915_gem_obj_alloc();
	i915_gem_object_get_pages(obj);
	obj->madv = I915_MADV_DONTNEED;

If so, I don't understand . _get is returning obj and it'll be needed so 
would expect to set 'obj->madv = I915_MADV_WILLNEED' which is the case now.

For this feedback, would appreciate it if you could provide comments or 
proposed solutions in line w/ source. That would be helpful for me to 
get whatever context I'm missing.

Re: Squash

OK. I didn't see this feedback. Will do.

Thanks,
-Mike

> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-12-01 22:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 21:53 [PATCH v5 0/7] Command parser batch buffer copy michael.h.nguyen
2014-11-26 21:53 ` [PATCH v5 1/7] drm/i915: Implement a framework for batch buffer pools michael.h.nguyen
2014-12-08 15:19   ` Bloomfield, Jon
2014-12-08 18:29     ` Michael H. Nguyen
2014-11-26 21:53 ` [PATCH v5 2/7] drm/i915: Use batch pools with the command parser michael.h.nguyen
2014-11-26 21:53 ` [PATCH v5 3/7] drm/i915: Add a batch pool debugfs file michael.h.nguyen
2014-11-26 21:53 ` [PATCH v5 4/7] drm/i915: Add batch pool details to i915_gem_objects debugfs michael.h.nguyen
2014-11-26 21:53 ` [PATCH v5 5/7] drm/i915: Use batch length instead of object size in command parser michael.h.nguyen
2014-11-26 21:53 ` [PATCH v5 6/7] drm/i915: Mark shadow batch buffers as purgeable michael.h.nguyen
2014-11-26 21:53 ` [PATCH v5 7/7] drm/i915: Tidy up execbuffer command parsing code michael.h.nguyen
2014-11-27  7:44 ` [PATCH v5 0/7] Command parser batch buffer copy Chris Wilson
2014-12-01 22:39   ` Michael H. Nguyen [this message]
2014-12-02  9:45     ` Daniel Vetter
2014-12-02 19:10       ` Michael H. Nguyen
2014-12-03  9:14         ` Daniel Vetter
2014-12-02 11:13     ` Chris Wilson
2014-12-02 12:57       ` Daniel Vetter
2014-12-02 21:57       ` Michael H. Nguyen
2014-12-03  9:17         ` Daniel Vetter
2014-12-03  9:31           ` Chris Wilson
2014-12-03 14:12             ` Daniel Vetter

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=547CEE37.40606@intel.com \
    --to=michael.h.nguyen@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 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.