From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] timer: fix reset on service cores
Date: Wed, 6 Sep 2017 09:25:34 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA640C7542D@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1503501537-12383-1-git-send-email-pbhagavatula@caviumnetworks.com>
> From: Pavan Nikhilesh [mailto:pbhagavatula@caviumnetworks.com]
> Sent: Wednesday, August 23, 2017 4:19 PM
> To: dev@dpdk.org
> Cc: Van Haaren, Harry <harry.van.haaren@intel.com>; Pavan Nikhilesh
> <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH] timer: fix reset on service cores
>
> - API rte_timer_reset() should be able to register timers on service
> lcores as they are EAL threads.
Nitpick comment: remove - at the start. (I'd ignore this, but v2 required based on below anyway..)
> Fixes: af75078fece3 ("first public release")
I'm not sure this is a fix to the first release.. service cores has only been added recently, I feel bad "git blaming" the first release :)
I suggest renaming the title to "timer: allow timer reset on service cores", and removing the Fixes: tag.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
With above changes,
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
> ---
> This patch depends on http://dpdk.org/dev/patchwork/patch/27818/
> lib/librte_timer/rte_timer.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/librte_timer/rte_timer.c b/lib/librte_timer/rte_timer.c
> index 5ee0840..a5a045c 100644
> --- a/lib/librte_timer/rte_timer.c
> +++ b/lib/librte_timer/rte_timer.c
> @@ -432,7 +432,8 @@ rte_timer_reset(struct rte_timer *tim, uint64_t ticks,
> uint64_t period;
>
> if (unlikely((tim_lcore != (unsigned)LCORE_ID_ANY) &&
> - !rte_lcore_is_enabled(tim_lcore)))
> + !(rte_lcore_is_enabled(tim_lcore) ||
> + rte_lcore_is_service_lcore(tim_lcore))))
> return -1;
>
> if (type == PERIODICAL)
> --
> 2.7.4
prev parent reply other threads:[~2017-09-06 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 15:18 Pavan Nikhilesh
2017-09-06 9:25 ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA640C7542D@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@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 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).