Skip to content

Add mechanism to select per block device cache strategy. #2207

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sandreim opened this issue Oct 20, 2020 · 1 comment · Fixed by #2447
Closed

Add mechanism to select per block device cache strategy. #2207

sandreim opened this issue Oct 20, 2020 · 1 comment · Fixed by #2447

Comments

@sandreim
Copy link
Contributor

sandreim commented Oct 20, 2020

We should investigate the opportunity and possibilities to allow customers to influence how host storage is being accessed in the Firecracker block device emulation. Here is a list of switches that might make sense to expose as configuration options:

  • ignore flush commands (from guest virtio driver) for performance reasons
  • use host page cache for read/write operations or prefer direct io with the block file
  • synchronous mode (O_SYNC/O_DSYNC) - writes will be reported complete only when committed to the host storage device
@berciuliviu
Copy link

Relates to 2223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants