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.

Sign up for GitHub

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

Jump to bottom

virtio-net: Add support for the flexible driver notification structure #73

Open
vmireyno-mvl opened this issue Mar 5, 2020 · 2 comments
Open

virtio-net: Add support for the flexible driver notification structure #73

vmireyno-mvl opened this issue Mar 5, 2020 · 2 comments

Comments

@vmireyno-mvl
Copy link
Contributor

vmireyno-mvl commented Mar 5, 2020 •
edited

Currently, the driver notification (available buffer notification) has a fixed structure.
If VIRTIO_F_NOTIFICATION_DATA has been negotiated, it includes: vqn, next_off and next_wrap.
If notify_off_multiplier > 0, the VQ number can be derived by the device from the Queue Notify address, so vqn may be redundant.
Some devices benefit from receiving an additional data with driver notifications. This data can optionally replace the vqn field in the driver notification structure.

The latest patch:
https://lists.oasis-open.org/archives/virtio-comment/202003/msg00019.html
@mstsirkin mstsirkin added the virtio-v1.2-cs01 To be fixed in the next release. label Mar 11, 2020
@mstsirkin
Copy link
Contributor

BALLOT CREATED AT URL: https://www.oasis-open.org/committees/ballot.php?id=3483

@vmireyno-mvl
Copy link
Contributor Author

The latest patch:
https://lists.oasis-open.org/archives/virtio-comment/202003/msg00028.html

@mstsirkin mstsirkin removed the virtio-v1.2-cs01 To be fixed in the next release. label Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mstsirkin @vmireyno-mvl