DPDK patches and discussions
 help / color / mirror / Atom feed
From: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DSW eventdev is getting "stuck"?
Date: Wed, 3 Apr 2019 18:36:29 +0000	[thread overview]
Message-ID: <3B32DEF7-8563-4BB5-BB01-0BFE29277B37@paloaltonetworks.com> (raw)
In-Reply-To: <8510f66d-a63e-4ef9-44e1-071758fec6fd@ericsson.com>



On 4/3/19, 11:34 AM, "Mattias Rönnblom" <mattias.ronnblom@ericsson.com> wrote:

    On 2019-04-03 20:17, Venky Venkatesh wrote:
    > Hi,
    > I am using the DSW code from 18.11 with the default settings for all the #defines. Here are some more details:
    > I have an 8 port system with 1 queue.
    > All ports can inject events. Port 0 and 7 inject events rarely.
    > Ports 1-6 are linked to the queue and hence dequeue events.
    > 
    > I see that in steady state the total number enqueues into the system is much greater than the total number of dequeues.
    > eventdev deq#: 1948491 enq#: 1949007
    > 
    
    If you have more enqueues than dequeues, it means there are events in 
    flight in the scheduler. In the above case, it's roughly 516 events, 
    which sounds perfectly healthy and normal. I say roughly, because 
    there's no way to take a consistent, global snapshot of all xstats counters.

[VV]: This is in steady state i.e. there are no more events being injected into the system. So shouldn’t everything get drained out at some point?
    
    You will see a higher value than this on dev_credits_on_loan, because 
    the ports will borrow (and return) credits in chunks of 64 to the shared 
    pool, for efficiently reasons.
 

   
    > However when I dump some of the data structure counters it doesn’t appear to be stuck. What may be going on?
    
    I'm guessing it doesn't appear stuck because it's not stuck.
    
    /M
    


  parent reply	other threads:[~2019-04-03 18:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 18:17 Venky Venkatesh
2019-04-03 18:17 ` Venky Venkatesh
2019-04-03 18:33 ` Mattias Rönnblom
2019-04-03 18:33   ` Mattias Rönnblom
2019-04-03 18:36   ` Venky Venkatesh [this message]
2019-04-03 18:36     ` Venky Venkatesh
2019-04-03 19:02     ` Mattias Rönnblom
2019-04-03 19:02       ` Mattias Rönnblom
2019-04-04  5:39       ` Venky Venkatesh
2019-04-04  5:39         ` Venky Venkatesh
2019-04-04  7:39         ` Mattias Rönnblom
2019-04-04  7:39           ` Mattias Rönnblom
2019-04-04 18:13           ` Venky Venkatesh
2019-04-04 18:13             ` Venky Venkatesh
2019-04-04 19:29             ` Mattias Rönnblom
2019-04-04 19:29               ` Mattias Rönnblom

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=3B32DEF7-8563-4BB5-BB01-0BFE29277B37@paloaltonetworks.com \
    --to=vvenkatesh@paloaltonetworks.com \
    --cc=dev@dpdk.org \
    --cc=mattias.ronnblom@ericsson.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).