All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Lauri Kasanen <cand@gmx.com>, Alex Deucher <alexdeucher@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
	Thomas Hellstrom <thellstrom@vmware.com>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/radeon: Use two-ended allocation by size, v2
Date: Wed, 02 Apr 2014 20:02:44 +0200	[thread overview]
Message-ID: <533C50C4.4000809@vodafone.de> (raw)
In-Reply-To: <20140402203342.b7b1b04a.cand@gmx.com>

Am 02.04.2014 19:33, schrieb Lauri Kasanen:
> This decreases eviction by up to 20%, by improving the fragmentation
> quality. No harm in normal cases that fit VRAM fully (PTS gaming suite).
>
> In some cases, even the VRAM-fitting cases improved slightly (openarena, urban terror).
>
> 512kb was measured as the most optimal threshold for 3d workloads common to radeon.
> Other drivers may need different thresholds according to their workloads.
>
> v2: Nicer formatting
> Signed-off-by: Lauri Kasanen <cand@gmx.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/gpu/drm/radeon/radeon_object.c | 13 ++++++++++++-
>   1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_object.c b/drivers/gpu/drm/radeon/radeon_object.c
> index 1375ff8..19bec0d 100644
> --- a/drivers/gpu/drm/radeon/radeon_object.c
> +++ b/drivers/gpu/drm/radeon/radeon_object.c
> @@ -104,7 +104,7 @@ bool radeon_ttm_bo_is_radeon_bo(struct ttm_buffer_object *bo)
>   
>   void radeon_ttm_placement_from_domain(struct radeon_bo *rbo, u32 domain)
>   {
> -	u32 c = 0;
> +	u32 c = 0, i;
>   
>   	rbo->placement.fpfn = 0;
>   	rbo->placement.lpfn = 0;
> @@ -131,6 +131,17 @@ void radeon_ttm_placement_from_domain(struct radeon_bo *rbo, u32 domain)
>   		rbo->placements[c++] = TTM_PL_MASK_CACHING | TTM_PL_FLAG_SYSTEM;
>   	rbo->placement.num_placement = c;
>   	rbo->placement.num_busy_placement = c;
> +
> +	/*
> +	 * 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] |= TTM_PL_FLAG_TOPDOWN;
> +		}
> +	}
>   }
>   
>   int radeon_bo_create(struct radeon_device *rdev,

      reply	other threads:[~2014-04-02 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 17:04 [PATCH 2/2] drm/radeon: Use two-ended allocation by size Lauri Kasanen
2014-04-02 17:08 ` Alex Deucher
2014-04-02 17:33   ` [PATCH] drm/radeon: Use two-ended allocation by size, v2 Lauri Kasanen
2014-04-02 18:02     ` Christian König [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=533C50C4.4000809@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexdeucher@gmail.com \
    --cc=cand@gmx.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=thellstrom@vmware.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.