DPDK patches and discussions
 help / color / mirror / Atom feed
From: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
To: harry.van.haaren@intel.com
Cc: jerin.jacob@caviumnetworks.com, narender.vangati@intel.com,
	gage.eads@intel.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH v1 0/1] Add service lcore attributes API
Date: Fri,  4 May 2018 15:16:03 -0500	[thread overview]
Message-ID: <1525464964-5342-1-git-send-email-erik.g.carrillo@intel.com> (raw)

This patch proposes the addition of an API which allows an application to
query the attributes of a service lcore.  It adds one such new attribute,
named "loops", which is a counter that tracks the number of times the service
core has looped in the service runner function (the driver function that
invokes services mapped to a service core).  This is useful to applications
that desire a "liveness" check to make sure a service core is not stuck.

Erik Gabriel Carrillo (1):
  service: Add service lcore attr APIs

 lib/librte_eal/common/include/rte_service.h | 30 ++++++++++++
 lib/librte_eal/common/rte_service.c         | 43 ++++++++++++++++-
 lib/librte_eal/rte_eal_version.map          |  2 +
 test/test/test_service_cores.c              | 73 +++++++++++++++++++++++++++++
 4 files changed, 147 insertions(+), 1 deletion(-)

-- 
2.6.4

             reply	other threads:[~2018-05-04 20:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 20:16 Erik Gabriel Carrillo [this message]
2018-05-04 20:16 ` [dpdk-dev] [PATCH v1 1/1] service: Add service lcore attr APIs Erik Gabriel Carrillo
2018-05-09 15:19   ` Van Haaren, Harry
2018-05-09 15:22     ` Carrillo, Erik G
2018-05-09 16:22 ` [dpdk-dev] [PATCH v2 " Erik Gabriel Carrillo
2018-07-11 21:44   ` Thomas Monjalon

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=1525464964-5342-1-git-send-email-erik.g.carrillo@intel.com \
    --to=erik.g.carrillo@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=narender.vangati@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).