From patchwork Thu Dec 6 09:30:33 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Anatoly Burakov X-Patchwork-Id: 48559 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 669665F1F; Thu, 6 Dec 2018 10:30:39 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 2DEEE5B3A; Thu, 6 Dec 2018 10:30:36 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Dec 2018 01:30:36 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,321,1539673200"; d="scan'208";a="281404304" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga005.jf.intel.com with ESMTP; 06 Dec 2018 01:30:34 -0800 Received: from sivswdev01.ir.intel.com (sivswdev01.ir.intel.com [10.237.217.45]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id wB69UXj6017363; Thu, 6 Dec 2018 09:30:34 GMT Received: from sivswdev01.ir.intel.com (localhost [127.0.0.1]) by sivswdev01.ir.intel.com with ESMTP id wB69UXZR027503; Thu, 6 Dec 2018 09:30:33 GMT Received: (from aburakov@localhost) by sivswdev01.ir.intel.com with LOCAL id wB69UXQa027499; Thu, 6 Dec 2018 09:30:33 GMT From: Anatoly Burakov To: dev@dpdk.org Cc: John McNamara , Marko Kovacevic , stable@dpdk.org Date: Thu, 6 Dec 2018 09:30:33 +0000 Message-Id: X-Mailer: git-send-email 1.7.0.7 Subject: [dpdk-dev] [PATCH] doc: remove note on limitations for memory mode in secondary X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Memory mode flags are now shared between primary and secondary processes, so the in documentation about limitations is no longer necessary. Fixes: 64cdfc35aaad ("mem: store memory mode flags in shared config") Cc: stable@dpdk.org Signed-off-by: Anatoly Burakov --- doc/guides/prog_guide/env_abstraction_layer.rst | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst index 8b5d050c7..426acfc28 100644 --- a/doc/guides/prog_guide/env_abstraction_layer.rst +++ b/doc/guides/prog_guide/env_abstraction_layer.rst @@ -147,15 +147,6 @@ A default validator callback is provided by EAL, which can be enabled with a ``--socket-limit`` command-line option, for a simple way to limit maximum amount of memory that can be used by DPDK application. -.. note:: - - In multiprocess scenario, all related processes (i.e. primary process, and - secondary processes running with the same prefix) must be in the same memory - modes. That is, if primary process is run in dynamic memory mode, all of its - secondary processes must be run in the same mode. The same is applicable to - ``--single-file-segments`` command-line option - both primary and secondary - processes must shared this mode. - + Legacy memory mode This mode is enabled by specifying ``--legacy-mem`` command-line switch to the