multithreading - What run-time issues are present when using thread-level memory-protection/paging? -

OK, so we support memory paging / protection per process today I have been thinking for years that today's basis But on the basis of page-level security, the smallest unit supporting our OS, how the profit is obtained: threads This brings me back to the forefront

Page-level thread-owned profits

• OS support to lock the page that is being accessed
• In theory, the security against memory corruption was a mechanism to take ownership for the life of a thread in the OS.

Downsides:

• Difficulty detection with standard locking technology is difficult to detect
• To determine page-level ownership Debugger / OS support

Any other downsides, updates that you can see from supporting such a model?

This type of programming model is already possible with processes and shared memory for good reason Not done: Interpreting is more secure and easier about passing messages.