From: Thomas Monjalon <thomas@monjalon.net>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org, Jasvinder Singh <jasvinder.singh@intel.com>
Subject: Re: [PATCH v3] net/softnic: add support for service cores
Date: Thu, 10 Jan 2019 16:06:04 +0100 [thread overview]
Message-ID: <12279762.qgYkyOx5tf@xps> (raw)
In-Reply-To: <20190110132625.118111-1-cristian.dumitrescu@intel.com>
10/01/2019 14:26, Cristian Dumitrescu:
> Add support to run the Soft NIC device on service cores, based on the
> value of the sc parameter:
>
> 0: The current Soft NIC device is run explicitly by the application. The
> firmware creates one or several pipelines for this dev and maps them
> to CPU cores that should not be service cores. The app is required to
> call rte_pmd_softnic_run() to make this dev work.
>
> 1 (default): The current device is run on the service cores transparently
> to the app. The firmware creates one or several pipelines for this dev
> current device and maps them to CPU cores that should be service cores.
> Each of these service cores is calling rte_pmd_softnic_run()
> in order to make this dev work with no app intervention.
>
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> ---
> Changes in v3:
> -re-added the commit message lost in v2 by mistake
>
> Changes in v2:
> -fixed compilation for some 32-bit targets by removing the need for
> function pointer conversion
Applied, thanks
prev parent reply other threads:[~2019-01-10 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 16:04 [PATCH] net/softnic: add support for service cores Cristian Dumitrescu
2019-01-07 16:50 ` Dumitrescu, Cristian
2019-01-09 23:23 ` Thomas Monjalon
2019-01-09 23:33 ` Thomas Monjalon
2019-01-10 11:36 ` [PATCH v2] " Cristian Dumitrescu
2019-01-10 13:26 ` [PATCH v3] " Cristian Dumitrescu
2019-01-10 15:06 ` Thomas Monjalon [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=12279762.qgYkyOx5tf@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.