[SERVER-10300] Add support for proper page fault handling to the new update framework Created: 23/Jul/13  Updated: 02/Aug/18  Resolved: 31/Jul/13

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: None
Fix Version/s: 2.5.2

Type: Task Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-10301 Add support for yielding on non-atomi... Closed
Participants:

 Description   

The new update driver is not yet taking advantage of the "likelyInPhysicalMemory" heuristic and thus it may go on to page in with the lock held.

The tricky part here is that bubbling up a negative return for likelyInPhysicalMemory in the old code is done through an exception. A page not being in memory is a perfectly fine situation, though.

Once the new framework is swapped in (and probably as adjusting instance.cpp:receivedUpdate), the driver may use a status to report that scenario.



 Comments   
Comment by auto [ 31/Jul/13 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}

Message: SERVER-10300 Implement page fault handling logic for new update framwork
Branch: master
https://github.com/mongodb/mongo/commit/3646f02d1e89c9ab478a2a3ace18c48e237b2803

Generated at Thu Feb 08 03:22:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.