DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: liyang07 <liyang07@corp.netease.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"dev@openvswitch.org" <dev@openvswitch.org>
Subject: Re: [dpdk-dev] About : Enable optional dequeue zero copy for vHost User
Date: Tue, 23 Jan 2018 10:46:27 +0000	[thread overview]
Message-ID: <74F120C019F4A64C9B78E802F6AD4CC278E853FF@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <D9CE3E0C-76CD-42E5-A716-D5F9D336BAD6@corp.netease.com>

Hi,

For the meantime this feature is proposed as ‘experimental’ for OVS DPDK.
Unless you are transmitting to a NIC, you don’t need to set the n_txq_desc.
My testing has been only with a DPDK driver in the guest. Have you tried that option?

Thanks,
Ciara

From: liyang07 [mailto:liyang07@corp.netease.com]
Sent: Wednesday, January 17, 2018 10:41 AM
To: Loftus, Ciara <ciara.loftus@intel.com>
Cc: dev@dpdk.org
Subject: About : Enable optional dequeue zero copy for vHost User


Hi Ciara,

    I am tesing the function of "vHost dequeue zero copy" for vm2vm on a host, and I have some problems:

    1. The networking is OK before run iperf, I can ping successed from vm1 to vm2,but after run iperf, the networking between vm1 and vm2 is down;(I think n_txq_desc cause the problem)

    2. I know the limitation about n_txq_desc, but I cannot set the n_txq_desc for dpdkport while the vms on the same host, because there is no dpdkports work fow my testing;



    Thus, how can I resolve it, thanks.





       reply	other threads:[~2018-01-23 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D9CE3E0C-76CD-42E5-A716-D5F9D336BAD6@corp.netease.com>
2018-01-23 10:46 ` Loftus, Ciara [this message]
2018-01-23 11:49   ` Chen, Junjie J

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=74F120C019F4A64C9B78E802F6AD4CC278E853FF@IRSMSX106.ger.corp.intel.com \
    --to=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=dev@openvswitch.org \
    --cc=liyang07@corp.netease.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).