From: Daniel Vetter <daniel@ffwll.ch>
To: "Pan, Xinhui" <Xinhui.Pan@amd.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: Cleanup TTMs delayed delete handling
Date: Tue, 11 Feb 2020 12:13:21 +0100 [thread overview]
Message-ID: <20200211111321.GY43062@phenom.ffwll.local> (raw)
In-Reply-To: <SN6PR12MB2800BAF6444C0BC373C13E9087180@SN6PR12MB2800.namprd12.prod.outlook.com>
On Tue, Feb 11, 2020 at 11:06:53AM +0000, Pan, Xinhui wrote:
> [AMD Official Use Only - Internal Distribution Only]
Uh might want to fix your email setup.
-Daniel
>
> For patch 1/2/3/5/6
> Reviewed-by: xinhui pan <xinhui.pan@amd.com>
> ________________________________
> From: Christian König <ckoenig.leichtzumerken@gmail.com>
> Sent: Monday, February 10, 2020 11:09:01 PM
> To: Pan, Xinhui <Xinhui.Pan@amd.com>; amd-gfx@lists.freedesktop.org <amd-gfx@lists.freedesktop.org>; dri-devel@lists.freedesktop.org <dri-devel@lists.freedesktop.org>
> Subject: Cleanup TTMs delayed delete handling
>
> This series of patches cleans up TTMs delayed delete handling.
>
> The core of the new handling is that we new only have a single reference counter instead of two and use kref_get_unless_zero() to grab BOs from the LRU during eviction.
>
> This reduces the overhead of LRU moves and allows us to properly individualize the BOs reservation object during deletion to allow adding BOs for clearing memory, unmapping page tables etc..
>
> Please review and comment,
> Christian.
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-02-11 11:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 15:09 Cleanup TTMs delayed delete handling Christian König
2020-02-10 15:09 ` [PATCH 1/6] drm/ttm: refine ghost BO resv criteria Christian König
2020-02-10 15:09 ` [PATCH 2/6] drm/ttm: cleanup ttm_buffer_object_transfer Christian König
2020-02-10 15:09 ` [PATCH 3/6] drm/ttm: use RCU in ttm_bo_flush_all_fences Christian König
2020-02-10 15:09 ` [PATCH 4/6] drm/ttm: rework BO delayed delete Christian König
2020-02-11 5:26 ` Pan, Xinhui
2020-02-11 5:43 ` Pan, Xinhui
2020-02-11 13:41 ` Christian König
2020-02-10 15:09 ` [PATCH 5/6] drm/ttm: replace dma_resv object on deleted BOs v2 Christian König
2020-02-11 14:14 ` Daniel Vetter
2020-02-11 15:02 ` Pan, Xinhui
2020-02-11 15:23 ` Christian König
2020-02-11 15:36 ` Daniel Vetter
2020-02-11 15:15 ` Christian König
2020-02-10 15:09 ` [PATCH 6/6] drm/ttm: individualize resv objects before calling release_notify Christian König
2020-02-11 11:06 ` Cleanup TTMs delayed delete handling Pan, Xinhui
2020-02-11 11:13 ` Daniel Vetter [this message]
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=20200211111321.GY43062@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Xinhui.Pan@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox