All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Pitoiset <samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Karol Herbst <nouveau-lIBOoy2+GI7scQ4cX5LuPg@public.gmane.org>,
	nouveau
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 0/2] allow partly reclocking on chipset
Date: Wed, 13 Jan 2016 13:54:55 +0100	[thread overview]
Message-ID: <5696491F.2060801@gmail.com> (raw)
In-Reply-To: <1740366416.39011.1452689355925.JavaMail.open-xchange-KNm3LHm9FEhKTQ5g00o1eQ@public.gmane.org>



On 01/13/2016 01:49 PM, Karol Herbst wrote:
>> Samuel Pitoiset <samuel.pitoiset@gmail.com> hat am 13. Januar 2016 um 13:43
>> geschrieben:
>>
>> Hi!
>>
>> Did you check on different Fermi chipsets or only with one variant?
>
> currently I only checked that on my nvc1, but I thought I could just send the
> patches and it is easier for others to try it out this way.

Yeah, you need to have more feedbacks on different chips.
What about fixing memory reclocking instead of this series which is 
going to be somehow useless when this will be done?

I mean memory reclocking probably offers more performance increase that 
engine reclocking, no?

>
>>
>> Are you sure that engine reclocking works as expected on Fermi? Because
>> enabling it without a strong inspection sounds like a prediction and it
>> might not work.
>
> It seems to work, because I got a huge performance increase in
> gputest_pixmark_piano, check the second commit for details ;)

I did, but 5.1->6.4 for heaven is a good start, but definitely not a 
huge performance increase in my humble opinion. :-)

>
>>
>> On 01/13/2016 01:25 PM, Karol Herbst wrote:
>>> some chipset have working engine reclocking, but broken memory reclocking
>>> like
>>> Fermi. We should for now, add the functionality to allow partly reclocking
>>> for
>>> those.
>>>
>>> Allthough this doesn't give as much performance as one might wish, it is
>>> till
>>> noticeable and may improve performance enough to be noted.
>>>
>>> Karol Herbst (2):
>>> clk: seperate engine and memory reclock toggles
>>> clk: allow engine reclock on fermi
>>>
>>> drm/nouveau/include/nvkm/subdev/clk.h | 3 ++-
>>> drm/nouveau/nvkm/subdev/clk/base.c | 21 ++++++++++++++-------
>>> drm/nouveau/nvkm/subdev/clk/gf100.c | 3 ++-
>>> drm/nouveau/nvkm/subdev/clk/gk104.c | 3 ++-
>>> drm/nouveau/nvkm/subdev/clk/gk20a.c | 2 +-
>>> drm/nouveau/nvkm/subdev/clk/gt215.c | 2 +-
>>> drm/nouveau/nvkm/subdev/clk/mcp77.c | 3 ++-
>>> drm/nouveau/nvkm/subdev/clk/nv04.c | 2 +-
>>> drm/nouveau/nvkm/subdev/clk/nv40.c | 2 +-
>>> drm/nouveau/nvkm/subdev/clk/nv50.c | 2 +-
>>> drm/nouveau/nvkm/subdev/clk/priv.h | 6 ++++--
>>> 11 files changed, 31 insertions(+), 18 deletions(-)
>>>
>>
>> --
>> -Samuel

-- 
-Samuel
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2016-01-13 12:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 12:25 [PATCH 0/2] allow partly reclocking on chipset Karol Herbst
     [not found] ` <1452687945-3971-1-git-send-email-nouveau-lIBOoy2+GI7scQ4cX5LuPg@public.gmane.org>
2016-01-13 12:25   ` [PATCH 1/2] clk: seperate engine and memory reclock toggles Karol Herbst
2016-01-13 12:25   ` [PATCH 2/2] clk: allow engine reclock on fermi Karol Herbst
     [not found]     ` <1452687945-3971-3-git-send-email-nouveau-lIBOoy2+GI7scQ4cX5LuPg@public.gmane.org>
2016-01-13 17:52       ` Roy Spliet
2016-01-13 12:43   ` [PATCH 0/2] allow partly reclocking on chipset Samuel Pitoiset
     [not found]     ` <56964657.2080805-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-13 12:49       ` Karol Herbst
     [not found]         ` <1740366416.39011.1452689355925.JavaMail.open-xchange-KNm3LHm9FEhKTQ5g00o1eQ@public.gmane.org>
2016-01-13 12:54           ` Samuel Pitoiset [this message]
     [not found]             ` <5696491F.2060801-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-13 14:16               ` Karol Herbst

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=5696491F.2060801@gmail.com \
    --to=samuel.pitoiset-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=nouveau-lIBOoy2+GI7scQ4cX5LuPg@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.