All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Paauwe <bob.j.paauwe@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Configurable GT idle frequency
Date: Tue, 23 Apr 2019 11:05:24 -0700	[thread overview]
Message-ID: <20190423110524.5d91f983@bpaauwe-desk.fm.intel.com> (raw)
In-Reply-To: <155543018626.25605.16064819862290127133@skylake-alporthouse-com>

On Tue, 16 Apr 2019 16:56:26 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> Quoting Bob Paauwe (2019-04-16 00:05:26)
> > There are real-time use cases where having deterministic CPU processes
> > can be more important than GPU power/performance. Parking the GPU at a
> > specific freqency by setting idle, min and max prohibits the normal
> > dynamic GPU frequency switching which can introduce significant PCI-E
> > latency. This adds the ability to configure the GPU "idle" frequecy
> > using the same method that already exists for minimum and maximum
> > frequencies.  
> 
> What exactly is the problem? We never use idle frequency while active,
> always restarting at max(cur, rpe). So for the simple minded among us,
> where is the igt demonstrating the issue?
> -Chris

To follow up and close this.  When I requested more details on the use
case and data for this request, I was informed that a different
solution is being pursued and this patch is no longer needed.

Thanks for the reviews and comments.
Bob

-- 
--
Bob Paauwe                  
Bob.J.Paauwe@intel.com
IOTG / PED Software Organization
Intel Corp.  Folsom, CA
(916) 356-6193    

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

      reply	other threads:[~2019-04-23 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 23:05 [PATCH] drm/i915: Configurable GT idle frequency Bob Paauwe
2019-04-15 23:32 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-04-16  0:17 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-16  0:33 ` [PATCH] " Vanshidhar Konda
2019-04-16 15:30   ` Bob Paauwe
2019-04-16 15:48     ` Vanshidhar Konda
2019-04-16  2:09 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-04-16 15:56 ` [PATCH] " Chris Wilson
2019-04-23 18:05   ` Bob Paauwe [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=20190423110524.5d91f983@bpaauwe-desk.fm.intel.com \
    --to=bob.j.paauwe@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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.