DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xie, Huawei" <huawei.xie@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: Fix the vhost broken issue
Date: Fri, 17 Oct 2014 09:28:27 +0200
Message-ID: <4665765.pNYqlQvYlS@xps13> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F2C0119@SHSMSX101.ccr.corp.intel.com>

2014-10-17 03:19, Xie, Huawei:
> From: Ouyang, Changchun
> > From: Xie, Huawei
> > > I generated the vhost example patch based on vhost library, but find
> > > there is
> > > issue with --mergeable feature.
> > > Only thousands of packets could be sent.
> > > Then I tried the latest vhost example,  which is just before my vhost
> > > lib patch, I found that not only it has the issue Which is fixed by the
> > > following patch but the --mergeable feature also doesn't work.
> > > Haven't got the change to dig into it.
> > > 
> > > Hints here:
> > > 1. mbuf allocation failure after thousands of packets.
> > > 2. disable INC_VEC(vectore scatter receive) in configure could solve
> > > this.
> > > 3. tried sending the packets directly out after receiving from vmdq
> > > queue, it
> > > works.
> > > 
> > > Could you root cause the issue, Changchun? You could work on the most
> > > recent
> > > example.
> > 
> > No problem, I will investigate the root cause.
> > 
> > But before figuring out the root cause, I think we could add check in your new
> > sample to
> > Check the INC_VEC is enable or not, If it is enabled, print error message and hint
> > user
> > Disable it in config file if mergeable feature is triggered in vhost. Then this issue
> > should not
> > block you from sending out your vhost app patch.
> > 
> > Your vhost app patch will block my another patch about multicast feature as
> > your vhost lib patch delete the vhost sample app totally.
> > So expect your vhost app patch send out soon.
> 
> Thomas:
> Thoughts about this? Could I send example patch with this walk around?

Yes, please send the new example with this small workaround.
It's better than nothing.

-- 
Thomas

      reply	other threads:[~2014-10-17  7:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13  7:39 Ouyang Changchun
2014-10-13  7:48 ` Ouyang, Changchun
2014-10-15 19:20   ` Xie, Huawei
2014-10-17  3:15     ` Ouyang, Changchun
2014-10-17  3:19       ` Xie, Huawei
2014-10-17  7:28         ` Thomas Monjalon [this message]

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=4665765.pNYqlQvYlS@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git