From: "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>
To: "Betts, Ian" <ian.betts@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Betts, Ian" <ian.betts@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/2] examples: add performance thread sample application
Date: Wed, 18 Nov 2015 10:03:40 +0000 [thread overview]
Message-ID: <3042915272161B4EB253DA4D77EB373A14E1EF54@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1447762268-25980-1-git-send-email-ian.betts@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ibetts
> Sent: Tuesday, November 17, 2015 13:11
> To: dev@dpdk.org
> Cc: Betts, Ian
> Subject: [dpdk-dev] [PATCH v3 1/2] examples: add performance thread
> sample application
>
> From: Ian Betts <ian.betts@intel.com>
>
> This example comprises a layer 3 forwarding derivative intended to
> facilitate characterization of performance with different
> threading models, specifically:-
>
> 1. EAL threads running on different physical cores
> 2. EAL threads running on the same physical core
> 3. Lightweight threads running in an EAL thread
>
> Purpose and justification
>
> Since dpdk 2.0 it has been possible to assign multiple EAL threads to
> a physical core ( case 2 above ).
> Currently no example application has focused on demonstrating the
> performance constraints of differing threading models.
>
> Whilst purpose built applications that fully comprehend the DPDK
> single threaded programming model will always yield superior
> performance, the desire to preserve ROI in legacy code written for
> multithreaded operating environments makes lightweight threads
> (case 3 above) worthy of consideration.
>
> As well as aiding with legacy code reuse, it is anticipated that
> lightweight threads will make it possible to scale a multithreaded
> application with fine granularity allowing an application to more
> easily take advantage of headroom on EAL cores, or conversely occupy
> more cores, as dictated by system load.
>
> To explore performance with lightweight threads a simple cooperative
> scheduler subsystem is being included in this example application.
> If the expected benefits and use cases prove to be of value, it is
> anticipated that this lightweight thread subsystem would become a
> library in some future DPDK release.
>
> Signed-off-by: Ian Betts <ian.betts@intel.com>
> ---
Acked-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
prev parent reply other threads:[~2015-11-18 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 12:11 ibetts
2015-11-17 12:11 ` [dpdk-dev] [PATCH v3 2/2] examples: add pthread-shim in performance-thread sample app ibetts
2015-11-17 14:51 ` Mcnamara, John
2015-11-18 9:18 ` Betts, Ian
2015-11-18 9:51 ` Kulasek, TomaszX
2015-11-18 10:03 ` Kulasek, TomaszX [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=3042915272161B4EB253DA4D77EB373A14E1EF54@IRSMSX102.ger.corp.intel.com \
--to=tomaszx.kulasek@intel.com \
--cc=dev@dpdk.org \
--cc=ian.betts@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).