All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/6] drm/i915/ttm: pass along the I915_BO_ALLOC_CONTIGUOUS
Date: Tue, 8 Jun 2021 09:08:26 +0100	[thread overview]
Message-ID: <55432d48-fd10-4deb-5cb9-8c3d03089cef@intel.com> (raw)
In-Reply-To: <044baf68ef8e6fe11941fdb43a9ad404f46c6d3a.camel@linux.intel.com>

On 08/06/2021 08:26, Thomas Hellström wrote:
> Hi,
> 
> On Mon, 2021-06-07 at 19:22 +0100, Matthew Auld wrote:
>> Currently we just ignore the I915_BO_ALLOC_CONTIGUOUS flag, which is
>> fine since everything is already contiguous with the ttm range
>> manager.
>> However in the next patch we want to switch over to the ttm buddy
>> manager, where allocations are by default not contiguous.
>>
>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> ---
>>   drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 15 ++++++++++++---
>>   1 file changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> index 73d52df8f2be..0b0fce445e9b 100644
>> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> @@ -86,10 +86,18 @@ i915_ttm_select_tt_caching(const struct
>> drm_i915_gem_object *obj)
>>   
>>   static void
>>   i915_ttm_place_from_region(const struct intel_memory_region *mr,
>> -                          struct ttm_place *place)
>> +                          struct ttm_place *place,
>> +                          unsigned int flags)
>>   {
>>          memset(place, 0, sizeof(*place));
>>          place->mem_type = intel_region_to_ttm_type(mr);
>> +
>> +       switch(mr->type) {
>> +       case INTEL_MEMORY_LOCAL:
>> +               if (flags & I915_BO_ALLOC_CONTIGUOUS)
>> +                       place->flags = TTM_PL_FLAG_CONTIGUOUS;
>> +               break;
>> +       }
> 
> Do we need to restrict this to INTEL_MEMORY_LOCAL? While it doesn't
> currently make much sense for other memory regions, no point in not
> forwarding for all?

Yeah, don't see why not.

> 
> /Thomas
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 4/6] drm/i915/ttm: pass along the I915_BO_ALLOC_CONTIGUOUS
Date: Tue, 8 Jun 2021 09:08:26 +0100	[thread overview]
Message-ID: <55432d48-fd10-4deb-5cb9-8c3d03089cef@intel.com> (raw)
In-Reply-To: <044baf68ef8e6fe11941fdb43a9ad404f46c6d3a.camel@linux.intel.com>

On 08/06/2021 08:26, Thomas Hellström wrote:
> Hi,
> 
> On Mon, 2021-06-07 at 19:22 +0100, Matthew Auld wrote:
>> Currently we just ignore the I915_BO_ALLOC_CONTIGUOUS flag, which is
>> fine since everything is already contiguous with the ttm range
>> manager.
>> However in the next patch we want to switch over to the ttm buddy
>> manager, where allocations are by default not contiguous.
>>
>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> ---
>>   drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 15 ++++++++++++---
>>   1 file changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> index 73d52df8f2be..0b0fce445e9b 100644
>> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
>> @@ -86,10 +86,18 @@ i915_ttm_select_tt_caching(const struct
>> drm_i915_gem_object *obj)
>>   
>>   static void
>>   i915_ttm_place_from_region(const struct intel_memory_region *mr,
>> -                          struct ttm_place *place)
>> +                          struct ttm_place *place,
>> +                          unsigned int flags)
>>   {
>>          memset(place, 0, sizeof(*place));
>>          place->mem_type = intel_region_to_ttm_type(mr);
>> +
>> +       switch(mr->type) {
>> +       case INTEL_MEMORY_LOCAL:
>> +               if (flags & I915_BO_ALLOC_CONTIGUOUS)
>> +                       place->flags = TTM_PL_FLAG_CONTIGUOUS;
>> +               break;
>> +       }
> 
> Do we need to restrict this to INTEL_MEMORY_LOCAL? While it doesn't
> currently make much sense for other memory regions, no point in not
> forwarding for all?

Yeah, don't see why not.

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

  reply	other threads:[~2021-06-08  8:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 18:22 [PATCH 0/6] Add back the buddy allocator Matthew Auld
2021-06-07 18:22 ` [Intel-gfx] " Matthew Auld
2021-06-07 18:22 ` [PATCH 1/6] drm/i915/ttm: add ttm_buddy_man Matthew Auld
2021-06-07 18:22   ` [Intel-gfx] " Matthew Auld
2021-06-08  7:11   ` Thomas Hellström
2021-06-08  7:11     ` [Intel-gfx] " Thomas Hellström
2021-06-08  8:11     ` Matthew Auld
2021-06-08  8:11       ` [Intel-gfx] " Matthew Auld
2021-06-08  8:15       ` Thomas Hellström
2021-06-08  8:15         ` [Intel-gfx] " Thomas Hellström
2021-06-07 18:22 ` [PATCH 2/6] drm/i915/ttm: add i915_sg_from_buddy_resource Matthew Auld
2021-06-07 18:22   ` [Intel-gfx] " Matthew Auld
2021-06-08  7:19   ` Thomas Hellström
2021-06-08  7:19     ` [Intel-gfx] " Thomas Hellström
2021-06-07 18:22 ` [PATCH 3/6] drm/i915/ttm: Calculate the object placement at get_pages time Matthew Auld
2021-06-07 18:22   ` [Intel-gfx] " Matthew Auld
2021-06-07 18:22 ` [PATCH 4/6] drm/i915/ttm: pass along the I915_BO_ALLOC_CONTIGUOUS Matthew Auld
2021-06-07 18:22   ` [Intel-gfx] " Matthew Auld
2021-06-08  7:26   ` Thomas Hellström
2021-06-08  7:26     ` [Intel-gfx] " Thomas Hellström
2021-06-08  8:08     ` Matthew Auld [this message]
2021-06-08  8:08       ` Matthew Auld
2021-06-07 18:22 ` [PATCH 5/6] drm/i915/ttm: switch over to ttm_buddy_man Matthew Auld
2021-06-07 18:22   ` [Intel-gfx] " Matthew Auld
2021-06-08  7:34   ` Thomas Hellström
2021-06-08  7:34     ` [Intel-gfx] " Thomas Hellström
2021-06-08  7:39   ` Thomas Hellström
2021-06-08  7:39     ` [Intel-gfx] " Thomas Hellström
2021-06-08  8:13     ` Matthew Auld
2021-06-08  8:13       ` [Intel-gfx] " Matthew Auld
2021-06-07 18:22 ` [PATCH 6/6] drm/i915/ttm: restore min_page_size behaviour Matthew Auld
2021-06-07 18:22   ` [Intel-gfx] " Matthew Auld
2021-06-08  7:41   ` Thomas Hellström
2021-06-08  7:41     ` [Intel-gfx] " Thomas Hellström
2021-06-07 20:08 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add back the buddy allocator Patchwork

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=55432d48-fd10-4deb-5cb9-8c3d03089cef@intel.com \
    --to=matthew.auld@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.intel.com \
    /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.