DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@caviumnetworks.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] service: add API for service count per lcore
Date: Tue, 29 Aug 2017 17:46:49 +0530	[thread overview]
Message-ID: <20170829121647.GA11846@PBHAGAVATULA-LT> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA640C6DA98@IRSMSX102.ger.corp.intel.com>

On Tue, Aug 29, 2017 at 12:05:12PM +0000, Van Haaren, Harry wrote:
> > From: Pavan Nikhilesh [mailto:pbhagavatula@caviumnetworks.com]
> > Sent: Tuesday, August 29, 2017 12:00 PM
> > To: Van Haaren, Harry <harry.van.haaren@intel.com>
> > Cc: dev@dpdk.org; Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > Subject: [dpdk-dev] [PATCH v3] service: add API for service count per lcore
> >
> > This new API returns the number of services that are running on a specific
> > service core. It allows an application to decide which service core to run
> > a new service on.
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > ---
> >
> > v3 changes:
> >   - fix compilation issues with .map files
> >
> > v2 changes:
> >   - reword the commit title according to the check-git-log.sh
> >   - modify return types
> >   - add function to .map file
> >
> >  lib/librte_eal/bsdapp/eal/rte_eal_version.map   |  1 +
> >  lib/librte_eal/common/include/rte_service.h     | 13 +++++++++++++
> >  lib/librte_eal/common/rte_service.c             | 13 +++++++++++++
> >  lib/librte_eal/linuxapp/eal/rte_eal_version.map |  1 +
> >  4 files changed, 28 insertions(+)
> >
> > diff --git a/lib/librte_eal/bsdapp/eal/rte_eal_version.map
> > b/lib/librte_eal/bsdapp/eal/rte_eal_version.map
> > index aac6fd7..79e7d31 100644
> > --- a/lib/librte_eal/bsdapp/eal/rte_eal_version.map
> > +++ b/lib/librte_eal/bsdapp/eal/rte_eal_version.map
> > @@ -222,6 +222,7 @@ EXPERIMENTAL {
> >  	rte_service_is_running;
> >  	rte_service_lcore_add;
> >  	rte_service_lcore_count;
> > +	rte_service_lcore_count_services;
> >  	rte_service_lcore_del;
> >  	rte_service_lcore_list;
> >  	rte_service_lcore_reset_all;
> > diff --git a/lib/librte_eal/common/include/rte_service.h
> > b/lib/librte_eal/common/include/rte_service.h
> > index 7c6f738..9537ae5 100644
> > --- a/lib/librte_eal/common/include/rte_service.h
> > +++ b/lib/librte_eal/common/include/rte_service.h
> > @@ -374,6 +374,19 @@ int32_t rte_service_lcore_list(uint32_t array[], uint32_t n);
> >   * @warning
> >   * @b EXPERIMENTAL: this API may change without prior notice
> >   *
> > + * Get the numer of services running on the supplied lcore.
> > + *
> > + * @param Lcore Id of the service core.
> > + * @retval >=0 Number of services registered to this core.
> > + * @retval -EINVAL Invalid lcore provided
> > + * @retval -ENOTSUP The provided lcore is not a service core.
> > + */
> > +int32_t rte_service_lcore_count_services(uint32_t lcore);
>
> Building the documentation[1] fails, the  @param Lcore  should have be @param lcore  (note the non-capital L, to keep doxygen happy).
> Sorry for missing that last review.

No issue will generate a v4 with the fix.

>
> With that fix;
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> [1] I tested using this command: ./devtools/test-build.sh x86_64-native-linuxapp-clang+shared+next+debug

Thanks for the inputs :). -Pavan

>
>
> > +
> > +/**
> > + * @warning
> > + * @b EXPERIMENTAL: this API may change without prior notice
> > + *
> >   * Dumps any information available about the service. If service is NULL,
> >   * dumps info for all services.
> >   */
> > diff --git a/lib/librte_eal/common/rte_service.c b/lib/librte_eal/common/rte_service.c
> > index 7efb76d..616bad3 100644
> > --- a/lib/librte_eal/common/rte_service.c
> > +++ b/lib/librte_eal/common/rte_service.c
> > @@ -397,6 +397,19 @@ rte_service_lcore_list(uint32_t array[], uint32_t n)
> >  }
> >
> >  int32_t
> > +rte_service_lcore_count_services(uint32_t lcore)
> > +{
> > +	if (lcore >= RTE_MAX_LCORE)
> > +		return -EINVAL;
> > +
> > +	struct core_state *cs = &lcore_states[lcore];
> > +	if (!cs->is_service_core)
> > +		return -ENOTSUP;
> > +
> > +	return __builtin_popcountll(cs->service_mask);
> > +}
> > +
> > +int32_t
> >  rte_service_start_with_defaults(void)
> >  {
> >  	/* create a default mapping from cores to services, then start the
> > diff --git a/lib/librte_eal/linuxapp/eal/rte_eal_version.map
> > b/lib/librte_eal/linuxapp/eal/rte_eal_version.map
> > index 3a8f154..468c706 100644
> > --- a/lib/librte_eal/linuxapp/eal/rte_eal_version.map
> > +++ b/lib/librte_eal/linuxapp/eal/rte_eal_version.map
> > @@ -227,6 +227,7 @@ EXPERIMENTAL {
> >  	rte_service_is_running;
> >  	rte_service_lcore_add;
> >  	rte_service_lcore_count;
> > +	rte_service_lcore_count_services;
> >  	rte_service_lcore_del;
> >  	rte_service_lcore_list;
> >  	rte_service_lcore_reset_all;
> > --
> > 2.7.4
>

      reply	other threads:[~2017-08-29 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 11:00 Pavan Nikhilesh
2017-08-29 12:05 ` Van Haaren, Harry
2017-08-29 12:16   ` Pavan Nikhilesh Bhagavatula [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=20170829121647.GA11846@PBHAGAVATULA-LT \
    --to=pbhagavatula@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.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).