All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
	"erik.g.carrillo@intel.com" <erik.g.carrillo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v3] app/eventdev: detect deadlock for timer event producer
Date: Sun, 16 Dec 2018 16:59:48 +0000	[thread overview]
Message-ID: <f444d2d628815697509a302c652bf03fb018828f.camel@marvell.com> (raw)
In-Reply-To: <1543859294-24259-1-git-send-email-erik.g.carrillo@intel.com>

On Mon, 2018-12-03 at 11:48 -0600, Erik Gabriel Carrillo wrote:
> If timer events get dropped for some reason, the thread that launched
> producer and worker cores will never exit, because the deadlock check
> doesn't currently apply to the event timer adapter case. This commit
> fixes this.
> 
> Fixes: d008f20bce23 ("app/eventdev: add event timer adapter as a
> producer")
> 
> Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>


Applied to dpdk-next-eventdev/master. Thanks.


> ---
> v3:
>  - Forgot to add Jerin's ack line.
> v2:
>  - Add a fixline to commit message (Jerin)
> 
>  app/test-eventdev/test_perf_common.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/app/test-eventdev/test_perf_common.c b/app/test-
> eventdev/test_perf_common.c
> index 8618775..f99a6a6 100644
> --- a/app/test-eventdev/test_perf_common.c
> +++ b/app/test-eventdev/test_perf_common.c
> @@ -327,7 +327,8 @@ perf_launch_lcores(struct evt_test *test, struct
> evt_options *opt,
>                 }
> 
>                 if (new_cycles - dead_lock_cycles > dead_lock_sample
> &&
> -                               opt->prod_type == EVT_PROD_TYPE_SYNT)
> {
> +                   (opt->prod_type == EVT_PROD_TYPE_SYNT ||
> +                    opt->prod_type ==
> EVT_PROD_TYPE_EVENT_TIMER_ADPTR)) {
>                         remaining = t->outstand_pkts -
> processed_pkts(t);
>                         if (dead_lock_remaining == remaining) {
>                                 rte_event_dev_dump(opt->dev_id,
> stdout);
> --
> 2.6.4
> 

      reply	other threads:[~2018-12-16 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 21:38 [PATCH v1 1/1] test: fix build with GCC 4.8.5 Erik Gabriel Carrillo
2018-05-05  3:17 ` Jerin Jacob
2018-05-05  4:55 ` Stephen Hemminger
2018-05-07 18:15   ` Carrillo, Erik G
2018-05-07 19:12 ` [PATCH v2 " Erik Gabriel Carrillo
2018-05-09  9:07   ` Jerin Jacob
2018-12-03 16:21 ` [PATCH v2] app/eventdev: detect deadlock for timer event producer Erik Gabriel Carrillo
2018-12-03 17:48 ` [PATCH v3] " Erik Gabriel Carrillo
2018-12-16 16:59   ` Jerin Jacob Kollanukkaran [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=f444d2d628815697509a302c652bf03fb018828f.camel@marvell.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=jerin.jacob@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.