6,534
edits
Changes
m
kernel internals
{{UBC toc}}
[[Category: Kernel internals]]
This page describes a very promising way of beancounters optimization.
== Current accounting model ==
Basically allocation of any kind of resource looks like this:
<presource lang="c">
struct some_resource *get_the_resource(int amount)
{
return ret;
}
</presource>
We change this behaviour to work like this:
<presource lang="c">
struct some_resource *get_the_resource(int amount)
{
return NULL;
}
</presource>
The <code>charge_beancounter()</code> call is responsible for checking whether the user is allowed to get the requested amount of the resource, i.e. if the resource consumption level is lower than the limit set.
Obviously, this change slows down the original code, as <code>charge_beancounter() </code> takes some slow operations like taking locks. We have an idea of how to optimize this behavior.
== On-demand accounting basics ==
Let's look at example of how this will work with the user memory accounting.
Currently we account for the [[physpages]] resource. That , that is -- , the number of physical pages consumed by the a set of processes. The accounting hooks are placed inside the page faults fault handlers and hurt thus hurting the performance. The Currently accounting looks like this:<presource lang="c">
struct page *get_new_page(struct mm_struct *mm)
{
return NULL;
}
</presource>
However, we have a good upper estimation of the RSS size -- — that is the lenghts lengths of mappings of the processes. Since the physical pages can only be allocated within these mappgins mappings, the RSS value can never exceed the sum of theis lenghstheir lengths. The accounting will then look like this:<presource lang="c">
struct vm_area_struct *get_new_mapping(struct mm_struct *mm,
unsigned long pages)
return NULL;
}
</presource>We do not call the slow <code>charge_beancounter()</code> function in the page fault (<code>get_new_page()</code>). Instead we account for the upper estimation in <code>get_new_mapping()</code> call that happens rarely and thus increase do not affect the performance.
Note, that the <code>recalculate_the_rss()</code> is called to calculate the exact RSS value on the beancounter.