From: Lauri Kasanen <cand@gmx.com>
To: dri-devel@lists.freedesktop.org
Cc: Thomas Hellstrom <thellstrom@vmware.com>
Subject: [RFC 0/3] TTM priority queue logic
Date: Fri, 4 Apr 2014 16:52:24 +0300 [thread overview]
Message-ID: <20140404165224.a4856af5.cand@gmx.com> (raw)
Hi list, Thomas,
I'd like to know if this is going in the right direction.
I've implemented a priority queue on top of the kernel rb tree and
linked list. It's been tested well in userspace.
I hardcoded radeon to input the buffer size as the score. Nothing blew
up, games ran fine, and even got ~2% more fps on average*.
The only thing missing from this code is the "if score is too low, and
there is no room without eviction, tell driver so" logic.
- Lauri
* This is a fairly bad strategy, and according to my simulator achieves
16% worse results compared to LRU in heavier situations. The games
tested here all fit in VRAM, which should explain the improvement.
next reply other threads:[~2014-04-04 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 13:52 Lauri Kasanen [this message]
2014-04-04 14:44 ` [RFC 0/3] TTM priority queue logic Thomas Hellstrom
2014-04-07 12:25 ` Thomas Hellstrom
2014-04-07 14:39 ` Lauri Kasanen
2014-04-07 14:53 ` Thomas Hellstrom
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=20140404165224.a4856af5.cand@gmx.com \
--to=cand@gmx.com \
--cc=dri-devel@lists.freedesktop.org \
--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.