From: "Eads, Gage" <gage.eads@intel.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] example: add new service cores sample application
Date: Mon, 23 Oct 2017 14:58:42 +0000 [thread overview]
Message-ID: <9184057F7FC11744A2107296B6B8EB1E1400BB1C@FMSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <1508409071-17740-1-git-send-email-harry.van.haaren@intel.com>
> -----Original Message-----
> From: Van Haaren, Harry
> Sent: Thursday, October 19, 2017 5:31 AM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Mcnamara, John <john.mcnamara@intel.com>;
> Eads, Gage <gage.eads@intel.com>; Van Haaren, Harry
> <harry.van.haaren@intel.com>
> Subject: [PATCH v2] example: add new service cores sample application
>
> This commit adds a new sample app, which showcases the value of running
> services. In particular it allows the application to dynamically schedule services
> to service-cores.
>
> The sample app itself registers a number of dummy services, and applies
> different profiles to them at runtime. Note that this sample application does not
> forward any traffic - it demonstrates advanced usage of the service cores API.
>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
>
Acked-by: Gage Eads <gage.eads@intel.com>
next prev parent reply other threads:[~2017-10-23 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 13:23 [dpdk-dev] [PATCH] " Harry van Haaren
2017-10-13 22:20 ` Thomas Monjalon
2017-10-13 22:24 ` Thomas Monjalon
2017-10-19 10:04 ` Van Haaren, Harry
2017-10-19 10:31 ` [dpdk-dev] [PATCH v2] " Harry van Haaren
2017-10-23 14:58 ` Eads, Gage [this message]
2017-10-24 21:02 ` 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=9184057F7FC11744A2107296B6B8EB1E1400BB1C@FMSMSX108.amr.corp.intel.com \
--to=gage.eads@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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).