Uploaded image for project: 'OASIS Virtual I/O Device (VIRTIO) TC'
  1. OASIS Virtual I/O Device (VIRTIO) TC
  2. VIRTIO-100 Google feedback on draft 1
  3. VIRTIO-105

Virtio NET

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: virtio 1.0 csprd01
    • Fix Version/s: virtio 1.0 csprd03
    • Labels:
      None
    • Proposal:
      Hide

      None. I don't think we want to start with vendor-specific commands (better to have them reserved expictly with an explicit feature) and similalrly expanding the structure should be left until we need it:

      https://lists.oasis-open.org/archives/virtio-comment/201404/msg00013.html

      Show
      None. I don't think we want to start with vendor-specific commands (better to have them reserved expictly with an explicit feature) and similalrly expanding the structure should be left until we need it: https://lists.oasis-open.org/archives/virtio-comment/201404/msg00013.html
    • Resolution:
      Hide

      Closed as per 2014-04-20 meeting: https://lists.oasis-open.org/archives/virtio/201405/msg00034.html

      Show
      Closed as per 2014-04-20 meeting: https://lists.oasis-open.org/archives/virtio/201405/msg00034.html

      Description

      Virtio Net

      5.1.6.4 Control Virtqueue

      Could the virtio_net_ctrl
      ​ ​
      ​structure ​be split into an request and response structure
      ​ ​
      with​ command specific data present in both giving a space for the device to respond with data instead of just a boolean ack. Could a vendor specific command be added to allow for extensions?

        Attachments

          Activity

            People

            • Assignee:
              rusty Rusty Russell (Inactive)
              Reporter:
              rusty Rusty Russell (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: