On Fri, 7 Jul 2000, Sam Tregar wrote:
>> That is the problem I believe, is that the kernel needs to try and
>> determine using logic which process is the REAL bad guy. Next to
>> impossible...
>
>Perhaps I'm naive, but it doesn't seem all that hard in the average
>case. If the kernel had access to some sort of historical
>memory-usage data then it could do some simple analysis in OOM. I
>imagine it would be pretty easy to spot your run-of-the-mill infinite-loop
>allocator with a few seconds of data at hand.
>
>If this idea is to be persued there are two questions - where/how to
>gather the necessary historical traces and what analysis to perform to
>come up with the culprit most of the time.
>
>Good idea? Suitable for a first kernel project?
Not my cup of tea, but feel free by all means to try it out
yourself. I certainly would be greatful if something successful
resulted. Another good idea is to try and get a group of people
all interested and contribute to each others ideas. Better
chance of success that way.. A thousand eyes...
Good luck,
TTYL
-- Mike A. Harris Linux advocate Computer Consultant GNU advocate Capslock Consulting Open Source advocateI've overclocked my keyboard interface. It's quite messy dipping my hands into the mineral oil, but *MAN* is my keyboard ever fast now! - Anonymous Coward
- 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 : Fri Jul 07 2000 - 21:00:20 EST