Skip to content

Don't create new kernel during restore#13229

Open
copybara-service[bot] wants to merge 1 commit into
masterfrom
test/cl918553781
Open

Don't create new kernel during restore#13229
copybara-service[bot] wants to merge 1 commit into
masterfrom
test/cl918553781

Conversation

@copybara-service
Copy link
Copy Markdown

Don't create new kernel during restore

When runsc create is called, there was no indication whether the sandbox
is being created for a new workload or to restore from a checkpoint. In
case of restore, a new kernel doesn't need to be initialized.

A new flag is added (--for-restore) to indicate that the sandbox is being
created from a checkpoint and the kernel creation is skipped.

This saves about 35ms from restore time.

When `runsc create` is called, there was no indication whether the sandbox
is being created for a new workload or to restore from a checkpoint. In
case of restore, a new kernel doesn't need to be initialized.

A new flag is added (--for-restore) to indicate that the sandbox is being
created from a checkpoint and the kernel creation is skipped.

This saves about 35ms from restore time.

PiperOrigin-RevId: 918553781
@copybara-service copybara-service Bot added the exported Issue was exported automatically label May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

exported Issue was exported automatically

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant