search for: devicenorm

...only be > > > +transmitted when the peer has sufficient free buffer space for the payload. > > > > > > All packets associated with a stream flow MUST contain valid information in > > > \field{buf_alloc} and \field{fwd_cnt} fields. > > > > > > \devicenormative{\paragraph}{Device Operation: Buffer Space > > > Management}{Device Types / Socket Device / Device Operation / Buffer > > > Space Management} > > > -VIRTIO_VSOCK_OP_RW data packets MUST only be transmitted when the peer has > > > -sufficient free buffer spac...

...only be > > > +transmitted when the peer has sufficient free buffer space for the payload. > > > > > > All packets associated with a stream flow MUST contain valid information in > > > \field{buf_alloc} and \field{fwd_cnt} fields. > > > > > > \devicenormative{\paragraph}{Device Operation: Buffer Space > > > Management}{Device Types / Socket Device / Device Operation / Buffer > > > Space Management} > > > -VIRTIO_VSOCK_OP_RW data packets MUST only be transmitted when the peer has > > > -sufficient free buffer spac...

...ufficient free buffer space for the payload. > > > > > > > > > > All packets associated with a stream flow MUST contain valid information in > > > > > \field{buf_alloc} and \field{fwd_cnt} fields. > > > > > > > > > > \devicenormative{\paragraph}{Device Operation: Buffer Space Management}{Device Types / Socket Device / Device Operation / Buffer Space Management} > > > > > -VIRTIO_VSOCK_OP_RW data packets MUST only be transmitted when the peer has > > > > > -sufficient free buffer space for the...

...ufficient free buffer space for the payload. > > > > > > > > > > All packets associated with a stream flow MUST contain valid information in > > > > > \field{buf_alloc} and \field{fwd_cnt} fields. > > > > > > > > > > \devicenormative{\paragraph}{Device Operation: Buffer Space Management}{Device Types / Socket Device / Device Operation / Buffer Space Management} > > > > > -VIRTIO_VSOCK_OP_RW data packets MUST only be transmitted when the peer has > > > > > -sufficient free buffer space for the...

...> > > > > > > > > > > > > All packets associated with a stream flow MUST contain valid information in > > > > > > > \field{buf_alloc} and \field{fwd_cnt} fields. > > > > > > > > > > > > > > \devicenormative{\paragraph}{Device Operation: Buffer Space Management}{Device Types / Socket Device / Device Operation / Buffer Space Management} > > > > > > > -VIRTIO_VSOCK_OP_RW data packets MUST only be transmitted when the peer has > > > > > > > -sufficient free b...

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

This is the continuation of my proposal for virtio-iommu, the para- virtualized IOMMU. Here is a summary of the changes since last time [1]: * The virtio-iommu document now resembles an actual specification. It is split into a formal description of the virtio device, and implementation notes. Please find sources and binaries at [2]. * Added a probe request to describe to the guest different

This is the continuation of my proposal for virtio-iommu, the para- virtualized IOMMU. Here is a summary of the changes since last time [1]: * The virtio-iommu document now resembles an actual specification. It is split into a formal description of the virtio device, and implementation notes. Please find sources and binaries at [2]. * Added a probe request to describe to the guest different

...then driver *might* set ext. bits to -% garbage. But this extension would be negotiated with a feature bit -% anyway. If it's not, then device must assume that driver is 0.2 and must -% keep truncating the fields. - The driver SHOULD NOT use multiple descriptor chains for a single request. \devicenormative{\subsubsection}{Device operations}{Device Types / IOMMU Device / Device operations} @@ -321,12 +312,14 @@ to zero. The device MUST ignore reserved fields of the head and the tail of a request. -If the VIRTIO_IOMMU_F_INPUT_RANGE feature is offered, the device MUST -truncate the range descri...

...irtqueues (receiveq1\ldots receiveqN and + transmitq1\ldots transmitqN respectively) that can be configured + on the device once VIRTIO_NET_F_MQ is negotiated. + \field{max_virtqueue_pairs} is valid only if VIRTIO_NET_F_MQ is + set and can be read by the driver. + +\end{description} + \devicenormative{\subsubsection}{Device configuration layout}{Device Types / Network Device / Device configuration layout} The device MUST set \field{max_virtqueue_pairs} to between 1 and 0x8000 inclusive, -- --Victor

...T_MTU is + negotiated, the driver uses the \field{default_mtu} as an initial + value, and also reports MTU changes to the device by writes to + \field{default_mtu}. Such reporting can be used for debugging, + or it can be used for tunning MTU along the network. + \end{description} \devicenormative{\subsubsection}{Device configuration layout}{Device Types / Network Device / Device configuration layout} @@ -3165,6 +3181,9 @@ by the driver after negotiation. The device MUST set \field{max_virtqueue_pairs} to between 1 and 0x8000 inclusive, if it offers VIRTIO_NET_F_MQ. +The device MUST...

This is version 0.5 of the virtio-iommu specification, the paravirtualized IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. Please find the specification, LaTeX sources and pdf, at: git://linux-arm.org/virtio-iommu.git viommu/v0.5 http://linux-arm.org/git?p=virtio-iommu.git;a=blob;f=dist/v0.5/virtio-iommu-v0.5.pdf A detailed changelog since v0.4 follows. You can find

This is version 0.5 of the virtio-iommu specification, the paravirtualized IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. Please find the specification, LaTeX sources and pdf, at: git://linux-arm.org/virtio-iommu.git viommu/v0.5 http://linux-arm.org/git?p=virtio-iommu.git;a=blob;f=dist/v0.5/virtio-iommu-v0.5.pdf A detailed changelog since v0.4 follows. You can find