DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Guru Prasad <tirutaniguru.14391@gmail.com>, users@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Dpdk eventdev performance testing
Date: Mon, 20 Aug 2018 15:27:38 +0100	[thread overview]
Message-ID: <80d3c13f-8a00-781d-d8dc-8874e4646cf7@intel.com> (raw)
In-Reply-To: <CAM6kMHzE5_oOTsWrbZ=y1_R5QzMavBBwHb8TLzJOFCQW3_1iBw@mail.gmail.com>

On 8/18/2018 4:12 PM, Guru Prasad wrote:
> Hi All,
> 
> While testing performance with eventdev, I am seeing a crash in dpdk
> service core. Test scenario is given below
> 1) DPDK 1805
> 2 Eventdev ordered Queues & 2 Ports
> 2) 2 Workers threads + 1 Service core for running scheduling.
> 3) 1st worker is getting packet from NIC and enqueueing to Q1 *.... [PLEASE
> FILL THIS]*
> 4) Packet rate of 5.6Mpps (Pkt size 64 bytes)

Thanks Guru for reporting.

Would you mind submitting this to https://bugs.dpdk.org/, it helps us trace it
better.

Thanks,
ferruh

      reply	other threads:[~2018-08-20 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-18 15:12 Guru Prasad
2018-08-20 14:27 ` Ferruh Yigit [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=80d3c13f-8a00-781d-d8dc-8874e4646cf7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=tirutaniguru.14391@gmail.com \
    --cc=users@dpdk.org \
    /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).