All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] examples/power: fix oob frequency oscillations
Date: Tue, 06 Aug 2019 13:18:42 +0200	[thread overview]
Message-ID: <5316435.KtOK4V2HBz@xps> (raw)
In-Reply-To: <f24b9469-b160-a266-0066-dc71a6260e60@intel.com>

26/07/2019 12:15, Burakov, Anatoly:
> So it's biased towards scaling up quickly, but it's doing that over a 
> period. Please correct me if i'm wrong as i'm not really familiar with 
> this codebase, but, assuming the window size is long enough, you could 
> be missing opportunities to scale down? For example, if you get a short 
> burst of 1's followed by a long burst of zeroes, you're not scaling down 
> until you go through the entire buffer and overwrite all of the values. 
> I guess that's the point of oscillation prevention, but maybe you could 
> improve the "scale-up" part by only checking a few recent values, rather 
> than the entire buffer?

This patch is deferred to 19.11.




  reply	other threads:[~2019-08-06 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 13:18 [dpdk-dev] [PATCH v1] examples/power: fix oob frequency oscillations David Hunt
2019-07-26 10:15 ` Burakov, Anatoly
2019-08-06 11:18   ` Thomas Monjalon [this message]
2019-10-27 18:35     ` Thomas Monjalon
2019-10-29 14:05       ` Hunt, David
2019-11-01 23:00         ` Thomas Monjalon
2019-11-04 10:16           ` Burakov, Anatoly
2019-11-12  7:23 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=5316435.KtOK4V2HBz@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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.