feat(runtime): implement shared transactional memcard with async saves
Intrepid/Prometeu/Runtime/pipeline/pr-master This commit looks good
Intrepid/Prometeu/Runtime/pipeline/pr-master This commit looks good
This commit is contained in:
@@ -80,8 +80,8 @@ flush, disk-completion wait, guest event queue or reason argument is added.
|
||||
Host-owned in-flight work keeps its ownership until the service/host safely
|
||||
releases it; lifecycle failure does not simulate cancellation or free borrowed
|
||||
buffers. Native calls must return promptly: VM fuel only bounds bytecode and
|
||||
cannot preempt a blocked native/host call. Existing FS read/write and the current
|
||||
memcard commit backend are synchronous interfaces, so this implementation does
|
||||
not promise a wall-time bound for them. The new asynchronous memcard backend
|
||||
must expose bounded submission/polling independently; hooks can then submit an
|
||||
explicit commit without waiting for disk completion.
|
||||
cannot preempt a blocked native/host call. Existing FS read/write interfaces remain synchronous. Memcard commits use
|
||||
bounded admission and query calls on the shared asset/IO lane. BeforePause can
|
||||
submit a commit and return immediately; BeforeResume can query the retained
|
||||
result. The independent 500ms cancellation and 1s host escalation deadlines are
|
||||
defined by [save memory](08-save-memory-and-memcard.md).
|
||||
|
||||
Reference in New Issue
Block a user