Skip to content
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

Gripe when using non-raw block device #594

Merged
merged 1 commit into from
Jan 6, 2024

Conversation

pfmooney
Copy link
Collaborator

@pfmooney pfmooney commented Jan 5, 2024

If the S_IFBLK instance of a block device is used, rather than the S_IFCHR raw instance, flush operations can be very expensive as the OS is forced to walk the page cache looking for necessary work.

While we will not strictly forbid the operator from choosing to use such a device, we can at least admonish their choice in the logs.

Fixes #518

If the S_IFBLK instance of a block device is used, rather than the
S_IFCHR raw instance, flush operations can be very expensive as the OS
is forced to walk the page cache looking for necessary work.

While we will not strictly forbid the operator from choosing to use such
a device, we can at least admonish their choice in the logs.

Fixes oxidecomputer#518
@pfmooney pfmooney merged commit eb43ab3 into oxidecomputer:master Jan 6, 2024
10 checks passed
@pfmooney pfmooney deleted the block-gripe branch January 6, 2024 02:34
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 this pull request may close these issues.

Reduced pci-virtio-block performance
1 participant