[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [virtio] [OASIS Issue Tracker] (VIRTIO-105) Virtio NET
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> writes: > Rusty Russell created VIRTIO-105: > ------------------------------------ > > Summary: Virtio NET > Key: VIRTIO-105 > URL: https://tools.oasis-open.org/issues/browse/VIRTIO-105 > Project: OASIS Virtual I/O Device (VIRTIO) TC > Issue Type: Sub-task > Affects Versions: virtio 1.0 csprd01 > Reporter: Rusty Russell > Assignee: Rusty Russell > > > 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. It could, but it would simply be a documentation change as we have no current users who need that. > Could a vendor specific command be added to allow for extensions? Not sure how that would work? I'm happy for us to reserve some class on a demand basis, but if we just specify one as "vendor specific" how would it be differentiated and used? Cheers, Rusty.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]