Thomas, Can we not deprecate the per-cpu ondemand governor parameters? Thanks, Praveen On Tue, 18 May 2010 2:57pm, Chidambaram, Praveen <pchidamb@xxxxxxxxxxx> wrote: > Yes, I would like to retain these as per-core variables. > > Also, I would like to introduce the down_threshold as a configurable > variable. > > I have observed that to prevent the governor from jittering too much, > the downthreshold could set to something higher than 10 and helps save > a lot of power. > > Thanks, > Praveen > > > On Tue, 18 May 2010 2:35pm, Thomas Renninger <trenn@xxxxxxx> wrote: > > On Tuesday 18 May 2010 10:31:02 pm Thomas Renninger wrote: > > > On Tuesday 18 May 2010 10:10:56 pm Chidambaram, Praveen wrote: > > > > Hi, > > ... > > > > This may not be very usable for different cpus having different > > > > governor parameters. What would be the best way to introduce these > > > > core/cpu specific tunable parameters? > > > > > > The same way it was done before. > > > The code is still there. > > > /*** deprecated ***/ > > > or similar markers are around. > > And you need per_cpu variables to store and use these. > > But what would be an applicable per core variable? > > > > Thomas > > -- > > To unsubscribe from this list: send the line "unsubscribe cpufreq" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > -- > To unsubscribe from this list: send the line "unsubscribe cpufreq" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
