Fixed the subject.
> Date: Fri, 6 Oct 2017 14:40:15 +0800
> From: Yuanhan Liu
> To: Jan Scheurich
> Cc: "'dev@dpdk.org'"
> Subject: Re: [dpdk-dev] [PATCH v3] vhost: Expose virtio interrupt need
> on rte_vhost API
> Message-ID: <20171006064015.
On Sat, Sep 23, 2017 at 08:31:37PM +, Jan Scheurich wrote:
...
> +int rte_vhost_tx_interrupt_requested(int vid, uint16_t qid)
> +{
> + struct virtio_net *dev;
> + struct vhost_virtqueue *vq;
> +
> + dev = get_device(vid);
> + if (dev == NULL)
> + return 0;
> +
> +
Adding maintainers to Cc
On Sat, Sep 23, 2017 at 08:31:37PM +, Jan Scheurich wrote:
[...]
Today this information is hidden inside the rte_vhost library
and not accessible to users of the API. This patch adds a
function to the API to query it.
Since you add to the API please also document
i
Friendly reminder:
Could somebody please have a look at this patch now that the DPDK
summit is over?
Thanks, Jan
> -Original Message-
> From: Jan Scheurich
> Sent: Saturday, 23 September, 2017 22:32
> To: 'dev@dpdk.org'
> Subject: [PATCH v3] vhost: Expose virtio interrupt need on rte_vh
Performance tests with the OVS DPDK datapath have shown
that the tx throughput over a vhostuser port into a VM with
an interrupt-based virtio driver is limited by the overhead
incurred by virtio interrupts. The OVS PMD spends up to 30%
of its cycles in system calls kicking the eventfd. Also the
5 matches
Mail list logo
