From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 04/15] drm/i915/buddy: track available visible size
Date: Fri, 11 Feb 2022 10:25:56 +0100 [thread overview]
Message-ID: <ddeff2de-a804-0e2e-2fac-f2076fba4f36@linux.intel.com> (raw)
In-Reply-To: <20220210121313.701004-5-matthew.auld@intel.com>
On 2/10/22 13:13, Matthew Auld wrote:
> Track the total amount of available visible memory, and also track
> per-resource the amount of used visible memory. For now this is useful
> for our debug output, and deciding if it is even worth calling into the
> buddy allocator. In the future tracking the per-resource visible usage
> will be useful for when deciding if we should attempt to evict certain
> buffers.
>
> v2:
> - s/place->lpfn/lpfn/, that way we can avoid scanning the list if the
> entire range is already mappable.
> - Move the end declaration inside the if block(Thomas).
> - Make sure to also account for reserved memory.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 04/15] drm/i915/buddy: track available visible size
Date: Fri, 11 Feb 2022 10:25:56 +0100 [thread overview]
Message-ID: <ddeff2de-a804-0e2e-2fac-f2076fba4f36@linux.intel.com> (raw)
In-Reply-To: <20220210121313.701004-5-matthew.auld@intel.com>
On 2/10/22 13:13, Matthew Auld wrote:
> Track the total amount of available visible memory, and also track
> per-resource the amount of used visible memory. For now this is useful
> for our debug output, and deciding if it is even worth calling into the
> buddy allocator. In the future tracking the per-resource visible usage
> will be useful for when deciding if we should attempt to evict certain
> buffers.
>
> v2:
> - s/place->lpfn/lpfn/, that way we can avoid scanning the list if the
> entire range is already mappable.
> - Move the end declaration inside the if block(Thomas).
> - Make sure to also account for reserved memory.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
next prev parent reply other threads:[~2022-02-11 9:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 12:12 [Intel-gfx] [PATCH v2 00/15] Initial support for small BAR recovery Matthew Auld
2022-02-10 12:12 ` Matthew Auld
2022-02-10 12:12 ` [Intel-gfx] [PATCH v2 01/15] drm/i915: add io_size plumbing Matthew Auld
2022-02-10 12:12 ` Matthew Auld
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 02/15] drm/i915/ttm: require mappable by default Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:20 ` [Intel-gfx] " Thomas Hellström
2022-02-11 9:20 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 03/15] drm/i915: add I915_BO_ALLOC_GPU_ONLY Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:23 ` [Intel-gfx] " Thomas Hellström
2022-02-11 9:23 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 04/15] drm/i915/buddy: track available visible size Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:25 ` Thomas Hellström [this message]
2022-02-11 9:25 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 05/15] drm/i915/buddy: adjust res->start Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 06/15] drm/i915/buddy: tweak 2big check Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 07/15] drm/i915/selftests: mock test io_size Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 08/15] drm/i915/ttm: make eviction mappable aware Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 09/15] drm/i915/ttm: mappable migration on fault Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 10/15] drm/i915/selftests: exercise mmap migration Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:36 ` [Intel-gfx] " Thomas Hellström
2022-02-11 9:36 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 11/15] drm/i915/selftests: handle allocation failures Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:37 ` [Intel-gfx] " Thomas Hellström
2022-02-11 9:37 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 12/15] drm/i915/create: apply ALLOC_GPU_ONLY by default Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:49 ` [Intel-gfx] " Thomas Hellström
2022-02-11 9:49 ` Thomas Hellström
2022-02-11 9:52 ` [Intel-gfx] " Matthew Auld
2022-02-11 9:55 ` Thomas Hellström
2022-02-11 10:00 ` Matthew Auld
2022-02-11 10:14 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 13/15] drm/i915/uapi: add NEEDS_CPU_ACCESS hint Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 9:59 ` [Intel-gfx] " Thomas Hellström
2022-02-11 9:59 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 14/15] drm/i915/uapi: forbid ALLOC_GPU_ONLY for error capture Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 10:06 ` [Intel-gfx] " Thomas Hellström
2022-02-11 10:06 ` Thomas Hellström
2022-02-10 12:13 ` [Intel-gfx] [PATCH v2 15/15] drm/i915/lmem: don't treat small BAR as an error Matthew Auld
2022-02-10 12:13 ` Matthew Auld
2022-02-11 10:08 ` [Intel-gfx] " Thomas Hellström
2022-02-11 10:08 ` Thomas Hellström
2022-02-10 14:40 ` [Intel-gfx] [PATCH v2 00/15] Initial support for small BAR recovery Das, Nirmoy
2022-02-10 15:24 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Initial support for small BAR recovery (rev3) 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=ddeff2de-a804-0e2e-2fac-f2076fba4f36@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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.