On Mon, Jun 20, 2011 at 02:09:19PM -0700, David Rientjes wrote:

On Mon, 20 Jun 2011, Frantisek Hrbata wrote:

quoted

Add user id to the oom killer's "Killed process" message, so the user of the
killed process can be identified.

Notified in what way?  Unless you are using the memory controller, there's 
no userspace notification that an oom event has happened so nothing would 
know to scrape the kernel log for this information.

Agreed, but this is not primary about notification, but about the availability of
the information at all, even if it's just in the kernel log and there is no
realtime notification about it. If I'm not missing anything, now you are not
notified if some process is killed neither(unless as you mentioned, you use
eventfd for memory.oom_control). But you can always inspect the kernel log
afterwards when you find out that some process is not running and you want to
know what happened. And here you have the information that the process was
killed by the oom killer.

I guess the uid of the killed process can be identified from the dump_tasks
output, where it is presented along with other info. I think it is handy
to have the uid info directly in the "Killed process" message. 

This is used/requested by one of our customers and since I think it's a good
idea to have the uid info presented, I posted the patch here to see what do you
think about it.

Many thanks

We've had a long-time desire for an oom notifier, not only at the time of 
oom but when approaching it with configurable thresholds, that would 
wakeup a userspace daemon that might be polling on notifier.  That seems 
more useful for realtime notification of an oom event rather than relying 
on the kernel log?

-- 
Frantisek Hrbata

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>