From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe/sa: Drop hardcoded 4K guard in sub-allocator
Date: Wed, 18 Dec 2024 20:47:37 +0100 [thread overview]
Message-ID: <326e8edb-e38e-44d7-b078-2defaf01fbbf@intel.com> (raw)
In-Reply-To: <aeec7c51-b04b-4805-82bb-c5f2051178f7@intel.com>
On 18.12.2024 10:15, Matthew Auld wrote:
> On 17/12/2024 22:39, Matthew Brost wrote:
>> On Tue, Dec 17, 2024 at 11:22:46PM +0100, Michal Wajdeczko wrote:
>>> Any required prefetch guards are added during batch buffer
>>> allocations anyway.
>>>
>>
>> This should work but I think we actually want to do the opposite of
>> this - drop the prefetch pad in BB allocation. This would enable a more
>> optimial usage of each suballocation. I think that would work unless we
>> have an odd caching issue - if caching is a problem then maybe the BB is
>> a cacheline.
>
> Also would be good to update bb_prefetch(), since current prefetch value
> is too small for xe2+ on some engines, so the hardcoded 4K here was
> maybe saving the day.
since I don't what would be a good value for xe2+, I'll hold with this
patch until someone fixes the bb_prefetch()
>
>>
>> I haven't had time to try to out yet but I think we explore the above
>> option first. If I'm missing something and the above does not work, then
>> agree with this patch.
>>
>> Matt
>>
next prev parent reply other threads:[~2024-12-18 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 22:22 [PATCH] drm/xe/sa: Drop hardcoded 4K guard in sub-allocator Michal Wajdeczko
2024-12-17 22:39 ` Matthew Brost
2024-12-18 9:15 ` Matthew Auld
2024-12-18 19:47 ` Michal Wajdeczko [this message]
2024-12-19 4:16 ` Matthew Brost
2024-12-18 19:42 ` Michal Wajdeczko
2024-12-18 0:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-18 0:05 ` ✓ CI.checkpatch: " Patchwork
2024-12-18 0:06 ` ✓ CI.KUnit: " Patchwork
2024-12-18 0:24 ` ✓ CI.Build: " Patchwork
2024-12-18 0:26 ` ✓ CI.Hooks: " Patchwork
2024-12-18 0:28 ` ✓ CI.checksparse: " Patchwork
2024-12-18 1:02 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-18 10:42 ` ✗ Xe.CI.Full: failure " 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=326e8edb-e38e-44d7-b078-2defaf01fbbf@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox