dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: drop ttm two ended allocation
Date: Tue, 17 Mar 2015 18:51:37 +0100	[thread overview]
Message-ID: <550869A9.80303@vmware.com> (raw)
In-Reply-To: <1426607955-2397-1-git-send-email-alexander.deucher@amd.com>

On 03/17/2015 04:59 PM, Alex Deucher wrote:
> radeon_bo_create() calls radeon_ttm_placement_from_domain()
> before ttm_bo_init() is called.  radeon_ttm_placement_from_domain()
> uses the ttm bo size to determine when to select top down
> allocation but since the ttm bo is not initialized yet the
> check is always false.  It only took affect when buffers
> were validated later.  It also seemed to regress suspend
> and resume on some systems possibly due to it not
> taking affect in radeon_bo_create().
>
> radeon_bo_create() and radeon_ttm_placement_from_domain()
> need to be reworked substantially for this to be optimally
> effective.  Re-enable it at that point.
>
> Noticed-by: Oded Gabbay <oded.gabbay@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Cc: stable@vger.kernel.org

Minor nitpick: s/take affect/take effect/

/Thomas


> ---
>  drivers/gpu/drm/radeon/radeon_object.c | 11 -----------
>  1 file changed, 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_object.c b/drivers/gpu/drm/radeon/radeon_object.c
> index 43e0994..318165d 100644
> --- a/drivers/gpu/drm/radeon/radeon_object.c
> +++ b/drivers/gpu/drm/radeon/radeon_object.c
> @@ -173,17 +173,6 @@ void radeon_ttm_placement_from_domain(struct radeon_bo *rbo, u32 domain)
>  		else
>  			rbo->placements[i].lpfn = 0;
>  	}
> -
> -	/*
> -	 * Use two-ended allocation depending on the buffer size to
> -	 * improve fragmentation quality.
> -	 * 512kb was measured as the most optimal number.
> -	 */
> -	if (rbo->tbo.mem.size > 512 * 1024) {
> -		for (i = 0; i < c; i++) {
> -			rbo->placements[i].flags |= TTM_PL_FLAG_TOPDOWN;
> -		}
> -	}
>  }
>  
>  int radeon_bo_create(struct radeon_device *rdev,

      parent reply	other threads:[~2015-03-17 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 15:59 [PATCH] drm/radeon: drop ttm two ended allocation Alex Deucher
2015-03-17 16:13 ` Christian König
2015-03-17 17:51 ` Thomas Hellstrom [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=550869A9.80303@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=stable@vger.kernel.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