search for: receiveqn

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +4967,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +4967,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +5001,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +5001,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +5001,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +5001,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +5001,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +5001,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +4966,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...d buffers for - incoming packets are placed in the receiveq. +Packets are transmitted by placing them in the transmitq +\change_inserted 1986246365 1353593685 +0..transmitqN +\change_unchanged +, and buffers for incoming packets are placed in the receiveq +\change_inserted 1986246365 1353593692 +0..receiveqN +\change_unchanged +. In each case, the packet itself is preceeded by a header: \end_layout @@ -4861,6 +4966,17 @@ If VIRTIO_NET_F_MRG_RXBUF is negotiated, each buffer must be at least the struct virtio_net_hdr \family default . +\change_inserted 1986246365 1353594518 + +\end_layout + +\beg...

...#define VIRTIO_NET_S_LINK_UP 1 #define VIRTIO_NET_S_ANNOUNCE 2 \end{lstlisting} -The following driver-read-only field, \field{max_virtqueue_pairs} only exists if -VIRTIO_NET_F_MQ is set. This field specifies the maximum number -of each of transmit and receive virtqueues (receiveq1\ldots receiveqN -and transmitq1\ldots transmitqN respectively) that can be configured once VIRTIO_NET_F_MQ -is negotiated. - \begin{lstlisting} struct virtio_net_config { u8 mac[6]; @@ -3140,6 +3131,35 @@ struct virtio_net_config { }; \end{lstlisting} +\field{mac}, \field{status}, \field{max_virtque...

...1 > #define VIRTIO_NET_S_ANNOUNCE 2 > \end{lstlisting} > > -The following driver-read-only field, \field{max_virtqueue_pairs} only exists if > -VIRTIO_NET_F_MQ is set. This field specifies the maximum number > -of each of transmit and receive virtqueues (receiveq1\ldots receiveqN > -and transmitq1\ldots transmitqN respectively) that can be configured once VIRTIO_NET_F_MQ > -is negotiated. > - > \begin{lstlisting} > struct virtio_net_config { > u8 mac[6]; > @@ -3140,6 +3131,35 @@ struct virtio_net_config { > }; > \end{lstlisting} >...

...bits depends on two > > different feature flags. > > > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > > --- > > + > > +\item [\field{max_virtqueue_pairs}] tells the driver the maximum > > + number of each of virtqueues (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. > > + > &gt...

...bits depends on two > > different feature flags. > > > > Signed-off-by: Victor Kaplansky <victork at redhat.com> > > --- > > + > > +\item [\field{max_virtqueue_pairs}] tells the driver the maximum > > + number of each of virtqueues (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. > > + > &gt...

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

...u32 guest_cid; > __u32 max_virtqueue_pairs; > } __packed; > > The guest_cid field specifies the guest context id which likes the guest IP > address. The max_virtqueue_pairs field specifies the maximum number of receive > and transmit virtqueue pairs (receiveq0 ... receiveqN and transmitq0 ... > transmitqN respectively; N = max_virtqueue_pairs - 1 ) that can be configured. > The driver is free to use only one virtqueue pairs, or it can use more to > achieve better performance. How does the driver tell the device how many vqs it's planning on actually usin...

...or bi-directional protocols (in practice, TCP), a given network connection + can utilize both transmit and receive queues. + For best performance, packets from a single connection should utilize the + paired transmit and receive queues from the same virtqueue pair; for example + both transmitqN and receiveqN. + This rule makes it possible to optimize processing on the device side, + but this is not a hard requirement: devices should function correctly even + when this rule is not followed. +\end_layout + +\begin_layout Standard + +\change_inserted 1986246365 1346932658 +Driver selects an active steerin...

...or bi-directional protocols (in practice, TCP), a given network connection + can utilize both transmit and receive queues. + For best performance, packets from a single connection should utilize the + paired transmit and receive queues from the same virtqueue pair; for example + both transmitqN and receiveqN. + This rule makes it possible to optimize processing on the device side, + but this is not a hard requirement: devices should function correctly even + when this rule is not followed. +\end_layout + +\begin_layout Standard + +\change_inserted 1986246365 1346932658 +Driver selects an active steerin...

...max_virtqueue_pairs; I'd make this little endian. > } __packed; > > The guest_cid field specifies the guest context id which likes the guest IP > address. The max_virtqueue_pairs field specifies the maximum number of receive > and transmit virtqueue pairs (receiveq0 ... receiveqN and transmitq0 ... > transmitqN respectively; N = max_virtqueue_pairs - 1 ) that can be configured. > The driver is free to use only one virtqueue pairs, or it can use more to > achieve better performance. Don't we need a field for driver to specify the # of VQs? I note packets have...