DPDK usage discussions
 help / color / mirror / Atom feed
From: Tom Barbette <barbette@kth.se>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Yongseok Koh <yskoh@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Unregistered mempool in secondary
Date: Thu, 6 Dec 2018 17:27:58 +0000	[thread overview]
Message-ID: <1544117277917.57532@kth.se> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E45123697824FC9F1@IRSMSX109.ger.corp.intel.com>

> except for the fact that you shouldn't run your secondary process with the same coremask as primary (it will lead to mempool cache corruption, among other things).

If I don't touch any packet on the primary, this shouldn't cause any problem, right? We want to use all of the CPU cores for processing. The primary is only a controller.

Tom

  reply	other threads:[~2018-12-06 17:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 23:41 Tom Barbette
2018-12-06  7:18 ` Shahaf Shuler
2018-12-06  8:18   ` Tom Barbette
2018-12-06  9:21     ` Shahaf Shuler
2018-12-06  9:37       ` Tom Barbette
2018-12-06  9:54         ` Shahaf Shuler
2018-12-06 11:52           ` Tom Barbette
2018-12-06 13:45             ` Shahaf Shuler
2018-12-06 13:49               ` Burakov, Anatoly
2018-12-06 14:53                 ` Tom Barbette
2018-12-06 15:28                   ` Tom Barbette
2018-12-06 15:39                     ` Burakov, Anatoly
2018-12-06 17:27                       ` Tom Barbette [this message]
2018-12-06 17:50                         ` Cliff Burdick
2018-12-06 21:53                           ` Tom Barbette

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=1544117277917.57532@kth.se \
    --to=barbette@kth.se \
    --cc=anatoly.burakov@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=rasland@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=users@dpdk.org \
    --cc=yskoh@mellanox.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).