All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.william.auld@gmail.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 4/4] drm/i915/ttm: Use TTM for system memory
Date: Fri, 11 Jun 2021 17:34:05 +0100	[thread overview]
Message-ID: <CAM0jSHPZCDSWyfvYta4hQxDQi9oR=1CqHg1xD6aDrmz4bGXHiQ@mail.gmail.com> (raw)
In-Reply-To: <20210611145459.8576-5-thomas.hellstrom@linux.intel.com>

On Fri, 11 Jun 2021 at 15:55, Thomas Hellström
<thomas.hellstrom@linux.intel.com> wrote:
>
> For discrete, use TTM for both cached and WC system memory. That means
> we currently rely on the TTM memory accounting / shrinker. For cached
> system memory we should consider remaining shmem-backed, which can be
> implemented from our ttm_tt_populate calback. We can then also reuse our
> own very elaborate shrinker for that memory.
>
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Auld <matthew.william.auld@gmail.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 4/4] drm/i915/ttm: Use TTM for system memory
Date: Fri, 11 Jun 2021 17:34:05 +0100	[thread overview]
Message-ID: <CAM0jSHPZCDSWyfvYta4hQxDQi9oR=1CqHg1xD6aDrmz4bGXHiQ@mail.gmail.com> (raw)
In-Reply-To: <20210611145459.8576-5-thomas.hellstrom@linux.intel.com>

On Fri, 11 Jun 2021 at 15:55, Thomas Hellström
<thomas.hellstrom@linux.intel.com> wrote:
>
> For discrete, use TTM for both cached and WC system memory. That means
> we currently rely on the TTM memory accounting / shrinker. For cached
> system memory we should consider remaining shmem-backed, which can be
> implemented from our ttm_tt_populate calback. We can then also reuse our
> own very elaborate shrinker for that memory.
>
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-06-11 16:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 14:54 [PATCH v2 0/4] drm/i915: Move system memory to TTM for discrete Thomas Hellström
2021-06-11 14:54 ` [Intel-gfx] " Thomas Hellström
2021-06-11 14:54 ` [PATCH v2 1/4] drm/i915: Update object placement flags to be mutable Thomas Hellström
2021-06-11 14:54   ` [Intel-gfx] " Thomas Hellström
2021-06-11 16:14   ` Matthew Auld
2021-06-11 16:14     ` [Intel-gfx] " Matthew Auld
2021-06-11 14:54 ` [PATCH v2 2/4] drm/i915/ttm: Adjust gem flags and caching settings after a move Thomas Hellström
2021-06-11 14:54   ` [Intel-gfx] " Thomas Hellström
2021-06-11 16:29   ` Matthew Auld
2021-06-11 16:29     ` Matthew Auld
2021-06-12  8:23     ` Thomas Hellström
2021-06-12  8:23       ` Thomas Hellström
2021-06-11 14:54 ` [PATCH v2 3/4] drm/i915/ttm: Calculate the object placement at get_pages time Thomas Hellström
2021-06-11 14:54   ` [Intel-gfx] " Thomas Hellström
2021-06-11 15:42   ` Matthew Auld
2021-06-11 15:42     ` [Intel-gfx] " Matthew Auld
2021-06-11 14:54 ` [PATCH v2 4/4] drm/i915/ttm: Use TTM for system memory Thomas Hellström
2021-06-11 14:54   ` [Intel-gfx] " Thomas Hellström
2021-06-11 16:34   ` Matthew Auld [this message]
2021-06-11 16:34     ` Matthew Auld
2021-06-11 17:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Move system memory to TTM for discrete (rev2) Patchwork
2021-06-11 17:40 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-11 19:32 ` [Intel-gfx] ✗ Fi.CI.IGT: 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='CAM0jSHPZCDSWyfvYta4hQxDQi9oR=1CqHg1xD6aDrmz4bGXHiQ@mail.gmail.com' \
    --to=matthew.william.auld@gmail.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.