DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/eventdev: configure optimum event timers per timer adapter
Date: Fri, 8 Mar 2019 19:05:17 +0000	[thread overview]
Message-ID: <206a8b09305e7d25d18e48ba35cba06c409685a8.camel@marvell.com> (raw)
In-Reply-To: <20190228184822.11345-1-pbhagavatula@marvell.com>

On Thu, 2019-02-28 at 18:48 +0000, Pavan Nikhilesh Bhagavatula wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> 
> Previously, the total number of event timers per adapter was set to
> an
> arbitrary value, set it to mempool size instead as it defines the max
> event timers that can be armed.
> 
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---

Please fix the below git-checklog.sh issue

Headline too long:
	app/eventdev: configure optimum event timers per timer adapter

With above change:
Acked-by: Jerin Jacob <jerinj@marvell.com>

>  app/test-eventdev/test_perf_common.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/app/test-eventdev/test_perf_common.c b/app/test-
> eventdev/test_perf_common.c
> index 24ece75c3..8dbfd8181 100644
> --- a/app/test-eventdev/test_perf_common.c
> +++ b/app/test-eventdev/test_perf_common.c
> @@ -417,7 +417,7 @@ perf_event_timer_adapter_setup(struct test_perf
> *t)
>  			.timer_adapter_id = i,
>  			.timer_tick_ns = t->opt->timer_tick_nsec,
>  			.max_tmo_ns = t->opt->max_tmo_nsec,
> -			.nb_timers = 2 * 1024 * 1024,
> +			.nb_timers = t->opt->pool_sz,
>  			.flags = flags,
>  		};
>  

  reply	other threads:[~2019-03-08 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 18:48 Pavan Nikhilesh Bhagavatula
2019-03-08 19:05 ` Jerin Jacob Kollanukkaran [this message]
2019-03-11  6:49 ` [dpdk-dev] [PATCH v2] app/eventdev: configure optimum timers per adapter Pavan Nikhilesh Bhagavatula
2019-03-12  8:05   ` Jerin Jacob Kollanukkaran

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=206a8b09305e7d25d18e48ba35cba06c409685a8.camel@marvell.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=pbhagavatula@marvell.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).