From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>, Yan Freedland <YanF@Radware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK - VIRTIO performance problems
Date: Mon, 13 Oct 2014 03:09:57 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511862688@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20141012131738.GB3672@mhcomputing.net>
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
next prev parent reply other threads:[~2014-10-13 3:02 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 [this message]
2014-10-13 7:04 ` Yan Freedland
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=F52918179C57134FAEC9EA62FA2F962511862688@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=YanF@Radware.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).