On Sun, 12 Mar 2000, Adam wrote:
> > The idea I had a few weeks ago to solve the problem and so to find out the
> > hog (and that I'll experiment in real life 2.3.x soon) is to add a
> > per-task page fault rate (ala avg_slice). Once we'll know the page fault
> > rate and the time of the last fault per each process, we'll be almost able
> > to find out the memory hog without possible mistakes and we won't need
> > anything else.
>
> That sounds interesting. I would be interested to see actual
> statistic of the per task page faults.
It is definately interesting, HOWEVER the OOM rescue code is
only to be run in an emergency.
This means Linus probably doesn't want us running around making
the common case slower by gathering loads of statistics. Then
again, this may be a statistic the SAR people may be interested
in.
Also, it should be relatively simple to DoS a box running this
selection algorithm. Real programs will touch their memory all
the time and fault a lot, a malicious hog only has to allocate
memory and touch it once...
regards,
Rik
-- The Internet is not a network of computers. It is a network of people. That is its real strength.http://www.conectiva.com/ http://www.surriel.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:27 EST