hi, Viresh
thanks for your reply. :)
On 2015年07月07日 18:45, Viresh Kumar wrote:
> On 07-07-15, 18:29, Pan Xinhui wrote:
>>
>> Now policy has field of driver_data, we can use it to get rid of per_cpu
>> acpi_cpufreq_data.
>
> Instead:
> "Drivers can store their internal per-policy
On 07-07-15, 18:29, Pan Xinhui wrote:
>
> Now policy has field of driver_data, we can use it to get rid of per_cpu
> acpi_cpufreq_data.
Instead:
"Drivers can store their internal per-policy information in
policy->driver_data, lets use it."
> we have benefits after this replacing. 1) memory
Now policy has field of driver_data, we can use it to get rid of per_cpu
acpi_cpufreq_data.
we have benefits after this replacing. 1) memory saving. 2) policy is
shared by several cpus, per_cpu seems not correct. useing *driver_data*
is more reasonable. 3) fix a memory leak in
hi, Viresh
thanks for your reply. :)
On 2015年07月07日 18:45, Viresh Kumar wrote:
On 07-07-15, 18:29, Pan Xinhui wrote:
Now policy has field of driver_data, we can use it to get rid of per_cpu
acpi_cpufreq_data.
Instead:
Drivers can store their internal per-policy information in
On 07-07-15, 18:29, Pan Xinhui wrote:
Now policy has field of driver_data, we can use it to get rid of per_cpu
acpi_cpufreq_data.
Instead:
Drivers can store their internal per-policy information in
policy-driver_data, lets use it.
we have benefits after this replacing. 1) memory saving.
Now policy has field of driver_data, we can use it to get rid of per_cpu
acpi_cpufreq_data.
we have benefits after this replacing. 1) memory saving. 2) policy is
shared by several cpus, per_cpu seems not correct. useing *driver_data*
is more reasonable. 3) fix a memory leak in
6 matches
Mail list logo
