DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yan Freedland <YanF@Radware.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>,
	Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK - VIRTIO performance problems
Date: Mon, 13 Oct 2014 07:04:38 +0000	[thread overview]
Message-ID: <CEFFBC011B3590479939EA0B9311D215269122A2@ILMB1.corp.radware.com> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F962511862688@shsmsx102.ccr.corp.intel.com>

Hi

I found that what blocked me was actually the "nf_conntrack",
So enlarging the maximum there solved the issue.

Thanks 
Yan

-----Original Message-----
From: Ouyang, Changchun [mailto:changchun.ouyang@intel.com] 
Sent: Monday, October 13, 2014 6:10 AM
To: Matthew Hall; Yan Freedland
Cc: dev@dpdk.org; Ouyang, Changchun
Subject: RE: [dpdk-dev] DPDK - VIRTIO performance problems

Hi ,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Matthew Hall
> Sent: Sunday, October 12, 2014 9:18 PM
> To: Yan Freedland
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK - VIRTIO performance problems
> 
> On Sun, Oct 12, 2014 at 12:37:37PM +0000, Yan Freedland wrote:
> > Every ~2min traffic stopped completely and then immediately came back.
> > This happened in a periodic fashion.
> 
> To me it sounds like it could be similar to what I've seen when I ran 
> out of mbuf's or ran out of RX / TX descriptor entries. It could be 
> worth checking the error counters on the interfaces with DPDK and 
> Linux OS / ethtool to see what might be incrementing during the failed time periods.
> 

I didn't meet this issue before,
I am not sure if the following patch will fix this issue or not. Please try it.
http://dpdk.org/dev/patchwork/patch/779/

By the way, what kind of backend did you use?
User space vhost, or other backend?

Thanks
Changchun

      reply	other threads:[~2014-10-13  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 12:37 Yan Freedland
2014-10-12 13:17 ` Matthew Hall
2014-10-13  3:09   ` Ouyang, Changchun
2014-10-13  7:04     ` Yan Freedland [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=CEFFBC011B3590479939EA0B9311D215269122A2@ILMB1.corp.radware.com \
    --to=yanf@radware.com \
    --cc=changchun.ouyang@intel.com \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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).