Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Alex Shi
On 12/11/2013 11:31 PM, Frederic Weisbecker wrote: >> > OK, I'll bite... Why not just use CONFIG_NO_HZ_FULL_SYSIDLE=y with >> > CONFIG_NO_HZ_FULL_SYSIDLE_SMALL set to at least the number of CPUs on >> > your system? The default for CONFIG_NO_HZ_FULL_SYSIDLE_SMALL is eight. >> > This stuff is in

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Frederic Weisbecker
On Wed, Dec 11, 2013 at 07:25:38AM -0800, Paul E. McKenney wrote: > On Wed, Dec 11, 2013 at 07:00:13PM +0800, Alex Shi wrote: > > On 12/11/2013 02:28 PM, Alex Shi wrote: > > > Hi Frederic, > > > > > > Sorry for idiot of nohz_full. When we using this feature on my mobile > > > devices, we found

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Paul E. McKenney
On Wed, Dec 11, 2013 at 07:00:13PM +0800, Alex Shi wrote: > On 12/11/2013 02:28 PM, Alex Shi wrote: > > Hi Frederic, > > > > Sorry for idiot of nohz_full. When we using this feature on my mobile > > devices, we found this feature keep cpu0 in periodic tick mode. then the > > timer interrupt on

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Alex Shi
On 12/11/2013 02:28 PM, Alex Shi wrote: > Hi Frederic, > > Sorry for idiot of nohz_full. When we using this feature on my mobile > devices, we found this feature keep cpu0 in periodic tick mode. then the > timer interrupt on cpu0 is very higher than normal nohz mode. > that cause high power

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Alex Shi
On 12/11/2013 02:28 PM, Alex Shi wrote: Hi Frederic, Sorry for idiot of nohz_full. When we using this feature on my mobile devices, we found this feature keep cpu0 in periodic tick mode. then the timer interrupt on cpu0 is very higher than normal nohz mode. that cause high power consuming

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Paul E. McKenney
On Wed, Dec 11, 2013 at 07:00:13PM +0800, Alex Shi wrote: On 12/11/2013 02:28 PM, Alex Shi wrote: Hi Frederic, Sorry for idiot of nohz_full. When we using this feature on my mobile devices, we found this feature keep cpu0 in periodic tick mode. then the timer interrupt on cpu0 is very

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Frederic Weisbecker
On Wed, Dec 11, 2013 at 07:25:38AM -0800, Paul E. McKenney wrote: On Wed, Dec 11, 2013 at 07:00:13PM +0800, Alex Shi wrote: On 12/11/2013 02:28 PM, Alex Shi wrote: Hi Frederic, Sorry for idiot of nohz_full. When we using this feature on my mobile devices, we found this feature keep

Re: nohz_full left a periodic tick cpu issue

2013-12-11 Thread Alex Shi
On 12/11/2013 11:31 PM, Frederic Weisbecker wrote: OK, I'll bite... Why not just use CONFIG_NO_HZ_FULL_SYSIDLE=y with CONFIG_NO_HZ_FULL_SYSIDLE_SMALL set to at least the number of CPUs on your system? The default for CONFIG_NO_HZ_FULL_SYSIDLE_SMALL is eight. This stuff is in mainline,

nohz_full left a periodic tick cpu issue

2013-12-10 Thread Alex Shi
Hi Frederic, Sorry for idiot of nohz_full. When we using this feature on my mobile devices, we found this feature keep cpu0 in periodic tick mode. then the timer interrupt on cpu0 is very higher than normal nohz mode. that cause high power consuming cost. I found you have mention this on commit:

nohz_full left a periodic tick cpu issue

2013-12-10 Thread Alex Shi
Hi Frederic, Sorry for idiot of nohz_full. When we using this feature on my mobile devices, we found this feature keep cpu0 in periodic tick mode. then the timer interrupt on cpu0 is very higher than normal nohz mode. that cause high power consuming cost. I found you have mention this on commit: