99
edits
Changes
Added future plans and fixed the examples
Apparently, when the estimation exceeds the limit, we must switch to the slower mode, that will give us more presice value of the consumption level and (probably) allocate another portion of the resource.
== Examples Example ==Let's look at some examples example of how this will workwith the user memory accounting.=== The user memory ===
Currently we account for the [[physpages]] resource. That is -- the number of physical pages consumed by the processes. The accounting hooks are placed inside the page faults and hurt the performance. The accounting looks like this:
<pre>
Note, that the <code>recalculate_the_rss()</code> is called to calculate the exact RSS value on the beancounter.
== More things to do ==
In this model we switch from the fast acounting to the slow one. However, if the upper estimation becomes lower than the limit again we can switch back to the fast model. However, these switches are not very fast themselves, and being too frequent can hurt the performance instead of improving. So this would require some further investigations.
