From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david.hunt@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 8EBF31DB1
 for <dev@dpdk.org>; Thu, 30 Jun 2016 09:41:50 +0200 (CEST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga102.jf.intel.com with ESMTP; 30 Jun 2016 00:41:49 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.26,550,1459839600"; d="scan'208";a="727237413"
Received: from sie-lab-214-251.ir.intel.com (HELO silpixa373510.ir.intel.com)
 ([10.237.214.251])
 by FMSMGA003.fm.intel.com with ESMTP; 30 Jun 2016 00:41:48 -0700
From: David Hunt <david.hunt@intel.com>
To: dev@dpdk.org
Cc: olivier.matz@6wind.com, viktorin@rehivetech.com,
 jerin.jacob@caviumnetworks.com, shreyansh.jain@nxp.com
Date: Thu, 30 Jun 2016 08:41:40 +0100
Message-Id: <1467272502-56059-1-git-send-email-david.hunt@intel.com>
X-Mailer: git-send-email 2.5.5
In-Reply-To: <1466428091-115821-1-git-send-email-david.hunt@intel.com>
References: <1466428091-115821-1-git-send-email-david.hunt@intel.com>
Subject: [dpdk-dev] [PATCH v4 0/2] mempool: add stack mempool handler
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 07:41:51 -0000

This patch set adds a lifo stack handler to the external mempool
manager.

This patch utilises the mempool handler feature which allows the addition
of new mempool handlers to DPDK.

Performance Notes:
For the mempool_perf_autotest, there's ain average of 30% increase in
performance for the local cache use-case for 1 - 36 cores (results vary
within those tests between 10-45% gain, but with an average of 30% gain
over all the tests.).

However, for the tests with no local cache configured, throughput of the
enqueue/dequeue drops by about 30%, with the 36 core yelding the largest
drop of 40%. So this handler would not be recommended in no-cache
applications.

v4 changes:
  * Update the test to replace the custom handler test with the
    stack handler test rather than just adding a stack handler test.
    The custom handler code is very similar to the stack handler, so
    there's no need to have both.

v3 changes:
  * Updated based on the latest version (v15) of the Mempool Handler feature

v2 changes:
  * updated based on mailing list feedback (Thanks Stephen)
  * checkpatch fixes.

David Hunt (2)
  mempool: add stack (lifo) mempool handler
  test: migrate custom handler test to stack handler