All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Rodriguez <andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org,
	nhaehnle-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: [PATCH] Use LRU mapping policy for SDMA engines v2
Date: Mon, 27 Mar 2017 18:36:05 -0400	[thread overview]
Message-ID: <20170327223607.2878-1-andresx7@gmail.com> (raw)

Previously we discussed some issues with applying the LRU mapping policy
to the SDMA engines. Mainly, if both ring ids end up aliased to the same
HW block, the total transfer bandwith an application can achieve will be
severely impacted. E.g. an app uses one SDMA ring for upload and one for
download.

This small series prevents ring id aliasing and enables LRU mapping for the
DMA ip blocks.

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

             reply	other threads:[~2017-03-27 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 22:36 Andres Rodriguez [this message]
     [not found] ` <20170327223607.2878-1-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-27 22:36   ` [PATCH 1/2] drm/amdgpu: guarantee bijective mapping of ring ids for LRU Andres Rodriguez
     [not found]     ` <20170327223607.2878-2-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-27 23:18       ` Andres Rodriguez
2017-03-28 15:22       ` Nicolai Hähnle
2017-03-27 22:36   ` [PATCH 2/2] drm/amdgpu: use LRU mapping policy for SDMA engines Andres Rodriguez
     [not found]     ` <20170327223607.2878-3-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-28 15:23       ` Nicolai Hähnle

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=20170327223607.2878-1-andresx7@gmail.com \
    --to=andresx7-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org \
    --cc=nhaehnle-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.