All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lauri Kasanen <cand@gmx.com>
To: "Christian König" <deathsimple@vodafone.de>,
	"Dave Airlie" <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Inline r100_mm_rreg, -wreg, v3
Date: Thu, 10 Jul 2014 11:48:31 +0300	[thread overview]
Message-ID: <20140710114831.a89f9c83.cand@gmx.com> (raw)
In-Reply-To: <535406B7.3090309@vodafone.de>

On Sun, 20 Apr 2014 19:41:11 +0200
Christian König <deathsimple@vodafone.de> wrote:

> Am 20.04.2014 19:29, schrieb Lauri Kasanen:
> > This was originally un-inlined by Andi Kleen in 2011 citing size concerns.
> > Indeed, a first attempt at inlining it grew radeon.ko by 7%.
> >
> > However, 2% of cpu is spent in this function. Simply inlining it gave 1% more fps
> > in Urban Terror.
> >
> > v2: We know the minimum MMIO size. Adding it to the if allows the compiler to
> > optimize the branch out, improving both performance and size.
> >
> > The v2 patch decreases radeon.ko size by 2%. I didn't re-benchmark, but common sense
> > says perf is now more than 1% better.
> >
> > v3: Also change _wreg, make the threshold a define.
> >
> > Inlining _wreg increased the size a bit compared to v2, so now radeon.ko
> > is only 1% smaller.
> >
> > Signed-off-by: Lauri Kasanen <cand@gmx.com>
> 
> Reviewed-by: Christian König <christian.koenig@amd.com>

Ping. Although reviewed in April, seems this wasn't applied to any tree?

- Lauri

  reply	other threads:[~2014-07-10  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 17:29 [PATCH] drm/radeon: Inline r100_mm_rreg, -wreg, v3 Lauri Kasanen
2014-04-20 17:41 ` Christian König
2014-07-10  8:48   ` Lauri Kasanen [this message]
2014-07-10  8:55     ` Christian König
2014-07-10 17:17       ` Alex Deucher

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=20140710114831.a89f9c83.cand@gmx.com \
    --to=cand@gmx.com \
    --cc=airlied@gmail.com \
    --cc=deathsimple@vodafone.de \
    --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 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.