This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
To fill out this checklist, please add the following to the template call: | B1 <!-- Referencing and citations --> = y/n | B2 <!-- Coverage and accuracy --> = y/n | B3 <!-- Structure --> = y/n | B4 <!-- Grammar and style --> = y/n | B5 <!-- Supporting materials --> = y/n
This article has been rated as Mid-importance on the project's importance scale.
I snipped this paragraph because it's influenced by my bias, although it IS true, and does show both that ES has something PaX found useful, and that PaX is more accurate than ES (which hence could lead to "better," and thus to manifesting my obvious bias that I keep trying to make sure doesn't crop up in these things).
Recent PaX revisions use a similar method inspired by Exec Shield with PAGEEXEC to avoid the excess overhead that the kernel assisted MMU walking imposes. PaX will fall back to kernel assisted MMU walking in the cases where Exec Shield would fail, at the cost of CPU overhead.
This isn't a quote, just my own explaination of what went on.