Linux Filesystem, Storage, and Memory Management Summit, Day 2
Posted Apr 10, 2011 16:08 UTC (Sun) by ccurtis
Parent article: Linux Filesystem, Storage, and Memory Management Summit, Day 2
Page tables can occupy large amounts of kernel memory; [...] when a control group hits its limit. [...] The other way, though, is in the page fault handler; there is no way to return a failure status there. The best the controller can do is to send a segmentation fault signal; [...]
As an application programmer I'd hate to see a SEGV if the system was unable to page in memory. I think most people equate SEGV with a wild pointer and chances seem good that a debugger would show a pointer access somewhere nearby in an application backtrace.
Wouldn't SIGBUS be a more appropriate signal to send in this case?
to post comments)