From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] service: add attribute get and reset
Date: Thu, 11 Jan 2018 23:42:10 +0100 [thread overview]
Message-ID: <11318245.0hPmIhzONk@xps> (raw)
In-Reply-To: <1507114491-144338-1-git-send-email-harry.van.haaren@intel.com>
04/10/2017 12:54, Harry van Haaren:
> This patchset adds two new functions to the service cores API, allowing
> the service library to expose generic attributes about the services,
> and to reset them. These attributes can be the cycle counts that cores
> have spent in the service-function. The 3rd patch in the series adds a
> new attribute, enabling the application to retrieve the number of calls
> to any service.
>
> Harry van Haaren (3):
> service: add attribute get function
> service: add reset all attributes for service
> service: add attribute for number of invokations
Please could you rebase this series?
There is also a typo in title and code comment:
invokation -> invocation
next prev parent reply other threads:[~2018-01-11 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 10:54 Harry van Haaren
2017-10-04 10:54 ` [dpdk-dev] [PATCH 1/3] service: add attribute get function Harry van Haaren
2018-01-12 10:27 ` [dpdk-dev] [PATCH v2 " Harry van Haaren
2018-01-12 10:27 ` [dpdk-dev] [PATCH v2 2/3] service: add reset all attributes for service Harry van Haaren
2018-01-12 10:27 ` [dpdk-dev] [PATCH v2 3/3] service: add attribute for number of invocations Harry van Haaren
2018-01-12 11:49 ` [dpdk-dev] [PATCH v2 1/3] service: add attribute get function Thomas Monjalon
2017-10-04 10:54 ` [dpdk-dev] [PATCH 2/3] service: add reset all attributes for service Harry van Haaren
2017-10-04 10:54 ` [dpdk-dev] [PATCH 3/3] service: add attribute for number of invokations Harry van Haaren
2018-01-11 22:42 ` Thomas Monjalon [this message]
2018-01-12 10:01 ` [dpdk-dev] [PATCH 0/3] service: add attribute get and reset Van Haaren, Harry
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=11318245.0hPmIhzONk@xps \
--to=thomas@monjalon.net \
--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).