DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Marvin Liu <yong.liu@intel.com>,
	xiaolong.ye@intel.com, zhihong.wang@intel.com,
	eperezma@redhat.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: remove deferred shadow update
Date: Wed, 15 Apr 2020 16:15:31 +0200	[thread overview]
Message-ID: <c45701ca-513c-e6be-3c9d-ef36a463a69a@redhat.com> (raw)
In-Reply-To: <20200401212926.74989-1-yong.liu@intel.com>



On 4/1/20 11:29 PM, Marvin Liu wrote:
> Defer shadow ring update will help overall throughput when frontend
> much slower than backend. But that is not all the cases we faced now.
> In case like ovs-dpdk + dpdk virtio user, frontend will much faster
> than backend. Frontend may not be able to collect available descs when
> shadow update is deferred. Thus will harm RFC2544 performance.

I don't understand this comment. What is the difference in term of
performance between Qemu + Virtio PMD and Virtio-User PMD, as the
datapath is the same?

> Solution is just remove deferred shadow update, which will help RFC2544
> and fix potential issue with virtio net driver.

What is the potential issue?

Maxime


  parent reply	other threads:[~2020-04-15 14:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 21:29 Marvin Liu
2020-04-06  8:56 ` Wang, Yinan
2020-04-15 14:15 ` Maxime Coquelin [this message]
2020-04-15 14:55   ` Liu, Yong
2020-04-15 15:03     ` Maxime Coquelin
2020-04-16  0:29       ` Liu, Yong
2020-04-17  2:39 ` [dpdk-dev] [PATCH v2] vhost: fix " Marvin Liu
2020-04-17 13:29   ` Maxime Coquelin
2020-04-17 17:08   ` Maxime Coquelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c45701ca-513c-e6be-3c9d-ef36a463a69a@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=eperezma@redhat.com \
    --cc=xiaolong.ye@intel.com \
    --cc=yong.liu@intel.com \
    --cc=zhihong.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).