Re: [virtio-dev] [PATCH v14] virtio-net: support the virtqueue coalescing moderation

[Heng Qi <hengqi@linux.alibaba.com>]

å 2023/4/5 äå12:29, Halil Pasic åé:
> On Thu, 23 Mar 2023 23:24:22 +0800
> Heng Qi <hengqi@linux.alibaba.com> wrote:
>
> > +struct virtio_net_ctrl_coal_vq {
> > +    le16 vqn;
> > +    le16 reserved;
> > +    struct virtio_net_ctrl_coal coal;
> > +};
> > +
> >   #define VIRTIO_NET_CTRL_NOTF_COAL 6
> >    #define VIRTIO_NET_CTRL_NOTF_COAL_TX_SET  0
> >    #define VIRTIO_NET_CTRL_NOTF_COAL_RX_SET 1
> > + #define VIRTIO_NET_CTRL_NOTF_COAL_VQ_SET 2
> > + #define VIRTIO_NET_CTRL_NOTF_COAL_VQ_GET 3
> >   \end{lstlisting}
> >   
> >   Coalescing parameters:
> >   \begin{itemize}
> > +\item \field{vqn}: The virtqueue number of an enabled transmit or receive virtqueue.
> Just to be on the safe side: VIRTIO_F_NOTIF_CONFIG_DATA has been
> negotiated, and queue_select != queue_notify_data, is vqn supposed
> to contain queue_notify_data or the number/index that is used for
> queue_select (I'm talking about the PCI transport case)?

Queue event notification is based on transport, as we know, this should 
be discussed in the virtio transport chapter.
Virtqueue coalescing moderation uses the same vqn field as 
notifications, but this has a completely different meaning.
For example, when VIRTIO_F_NOTIF_CONFIG_DATA is negotiated, vqn uses the 
identifier (which Parav is doing) represented by q_notify_data,
such as virtqueue index/number or offset, etc.
vqn here does not belong to the PCI configuration space, because now we 
have involved controlq, which is used to set the non-configuration space.

Thanks.


> Regards,
> Halil