linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yu Chen <yu.c.chen@intel.com>
To: joeyli <jlee@suse.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org,
	Lenny Szubowicz <lszubowi@redhat.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Rui Zhang <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH][RFC v2] ACPI: acpi_pad: Do not launch acpi_pad threads on idle cpus
Date: Tue, 11 Dec 2018 11:12:21 +0800	[thread overview]
Message-ID: <20181211031220.GA23975@chenyu-desktop> (raw)
In-Reply-To: <20181210063153.GO5327@linux-l9pv.suse>

Hi Joey,
On Mon, Dec 10, 2018 at 02:31:53PM +0800, joeyli wrote:
> Hi Chen Yu and ACPI experts,
> 
> On Sat, May 05, 2018 at 07:53:22PM +0800, Chen Yu wrote:
> > According to current implementation of acpi_pad driver,
> > it does not make sense to spawn any power saving threads
> > on the cpus which are already idle - it might bring
> > unnecessary overhead on these idle cpus and causes power
> > waste. So verify the condition that if the number of 'busy'
> > cpus exceeds the amount of the 'forced idle' cpus is met.
> > This is applicable due to round-robin attribute of the
> > power saving threads, otherwise ignore the setting/ACPI
> > notification.
> > 
> > Suggested-by: Lenny Szubowicz <lszubowi@redhat.com>
> > Suggested-by: Len Brown <lenb@kernel.org>
> > Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> > Cc: Lenny Szubowicz <lszubowi@redhat.com>
> > Cc: Len Brown <lenb@kernel.org>
> > Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > Cc: Rui Zhang <rui.zhang@intel.com>
> > Cc: linux-acpi@vger.kernel.org
> > Signed-off-by: Chen Yu <yu.c.chen@intel.com>
> 
> Do you have any news for this patch? Why it did not merged by kernel
> maineline?
> 
We are evaluating if this could be integrated into idle injection framework.
May I know if there's any requirement/background from SUSE on this?

Best,
Ryan(Yu)
> Thanks a lot!
> Joey Lee
> 
> > ---
> >  drivers/acpi/acpi_pad.c | 52 ++++++++++++++++++++++++++++++++++++++++++++++++-
> >  1 file changed, 51 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/acpi/acpi_pad.c b/drivers/acpi/acpi_pad.c
> > index 552c1f7..515e60e 100644
> > --- a/drivers/acpi/acpi_pad.c
> > +++ b/drivers/acpi/acpi_pad.c
> > @@ -254,12 +254,62 @@ static void set_power_saving_task_num(unsigned int num)
> >  	}
> >  }
> >  
> > +/*
> > + * Extra acpi_pad threads should not be created until
> > + * the requested idle count is less than/equals to the
> > + * number of the busy cpus - it does not make sense to
> > + * throttle the idle cpus.
> > + */
> > +#define SAMPLE_INTERVAL_JIF	20
> > +
> > +static u64 get_idle_time(int cpu)
> > +{
> > +	u64 idle, idle_usecs = -1ULL;
> > +
> > +	idle_usecs = get_cpu_idle_time_us(cpu, NULL);
> > +
> > +	if (idle_usecs == -1ULL)
> > +		idle = kcpustat_cpu(cpu).cpustat[CPUTIME_IDLE];
> > +	else
> > +		idle = idle_usecs * NSEC_PER_USEC;
> > +
> > +	return idle;
> > +}
> > +
> > +static bool idle_nr_valid(unsigned int num_cpus)
> > +{
> > +	int busy_nr = 0, i = 0, load_thresh = 100 - idle_pct;
> > +
> > +	if (!num_cpus)
> > +		return true;
> > +
> > +	for_each_online_cpu(i) {
> > +		u64 wall_time, idle_time;
> > +		unsigned int elapsed_delta, idle_delta, load;
> > +
> > +		wall_time = jiffies64_to_nsecs(get_jiffies_64());
> > +		idle_time = get_idle_time(i);
> > +		/* Wait and see... */
> > +		schedule_timeout_uninterruptible(SAMPLE_INTERVAL_JIF);
> > +
> > +		idle_delta = get_idle_time(i) - idle_time;
> > +		elapsed_delta = jiffies64_to_nsecs(get_jiffies_64()) - wall_time;
> > +		idle_delta = (idle_delta > elapsed_delta) ? elapsed_delta : idle_delta;
> > +		load = 100 * (elapsed_delta - idle_delta) / elapsed_delta;
> > +		if (load >= load_thresh)
> > +			busy_nr++;
> > +	}
> > +
> > +	return (busy_nr >= num_cpus) ? true : false;
> > +}
> > +
> >  static void acpi_pad_idle_cpus(unsigned int num_cpus)
> >  {
> >  	get_online_cpus();
> >  
> >  	num_cpus = min_t(unsigned int, num_cpus, num_online_cpus());
> > -	set_power_saving_task_num(num_cpus);
> > +	if (idle_nr_valid(num_cpus))
> > +		set_power_saving_task_num(num_cpus);
> >  
> >  	put_online_cpus();
> >  }
> > -- 
> > 2.7.4
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-12-11  3:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 11:53 [PATCH][RFC v2] ACPI: acpi_pad: Do not launch acpi_pad threads on idle cpus Chen Yu
2018-05-13  9:30 ` Rafael J. Wysocki
2018-05-14 15:45   ` Yu Chen
2018-05-14 20:42     ` Rafael J. Wysocki
2018-10-03  9:38     ` Rafael J. Wysocki
2018-12-10  6:31 ` joeyli
2018-12-11  3:12   ` Yu Chen [this message]
2018-12-11  8:37     ` joeyli
2018-12-12  1:56       ` Yu Chen

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=20181211031220.GA23975@chenyu-desktop \
    --to=yu.c.chen@intel.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jlee@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lszubowi@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).