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 v2] app/eventdev: configure optimum timers per adapter
Date: Tue, 12 Mar 2019 08:05:22 +0000 [thread overview]
Message-ID: <4434e66e15a872213e41455f78a3d291fbee5b84.camel@marvell.com> (raw)
In-Reply-To: <20190311064900.4938-1-pbhagavatula@marvell.com>
On Mon, 2019-03-11 at 06:49 +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>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-eventdev/master. Thanks.
> ---
> 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 f99a6a607..d14034e52 100644
> --- a/app/test-eventdev/test_perf_common.c
> +++ b/app/test-eventdev/test_perf_common.c
> @@ -432,7 +432,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,
> };
>
prev parent reply other threads:[~2019-03-12 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 18:48 [dpdk-dev] [PATCH] app/eventdev: configure optimum event timers per timer adapter Pavan Nikhilesh Bhagavatula
2019-03-08 19:05 ` Jerin Jacob Kollanukkaran
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 [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=4434e66e15a872213e41455f78a3d291fbee5b84.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).