From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 79EA5A2EEB
	for <public@inbox.dpdk.org>; Mon,  7 Oct 2019 17:43:54 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 4FBE21C19B;
	Mon,  7 Oct 2019 17:43:53 +0200 (CEST)
Received: from mail-pg1-f193.google.com (mail-pg1-f193.google.com
 [209.85.215.193]) by dpdk.org (Postfix) with ESMTP id DE67E1C196
 for <dev@dpdk.org>; Mon,  7 Oct 2019 17:43:51 +0200 (CEST)
Received: by mail-pg1-f193.google.com with SMTP id x10so8455972pgi.5
 for <dev@dpdk.org>; Mon, 07 Oct 2019 08:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=networkplumber-org.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding;
 bh=6fsH6DS0qcMckcKE4Trofvu0NPdVy8lX/ZOXwIW3hX8=;
 b=WabTvuwg3cU3C+C2GVa7i0gcYZ2ET52sPEdi4y3dqGByjO71aBK4opQHuH4ta9NQt2
 p36uHAUVNnbyzVZZgHFITz5n0sXYY6YgmSv2CNTckujsW3LHC3MfBPArILP9z5VL1KTT
 kTcAiq24Z2eLM/pjVgXICPevNPIRuR1GN3hLAxsUSYhD7a37ZJenpa5HNgutgakUWFqV
 vLHeCscgAPCxg+4k6PR31jcAtgeg1GMo4fPh9UUtFwN7ePgf6ZrVaOiaUfepX8qOFeKU
 NhNdEM7qRXlOEyt5U6EX3tLJvM9QBGHg8Cn/gRp08kw02gguHhG/w4LHOXj5pDl3UxOW
 kLEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=6fsH6DS0qcMckcKE4Trofvu0NPdVy8lX/ZOXwIW3hX8=;
 b=a1TLJOm/azI0nTtEfWKK0sY94EWWW8uufNdnKaPJpXoSX5Aib8swDnBwE/lX3k7W86
 5p+/1g73LtZrrYI5k1gWKfLc08rw8g0tdFEDe8yhAiOBan4E1JfKA4J7kPseoqmyi72x
 O9QTL4iRKpwFx74Kh/aBi9Xv4QkEXBmxvDRq51NkR3XwUf/PMfPLBn3PBPf+svdYf/hY
 YbekUhfbvoIexLodlfVAk3CGaG79H7E3KlKOM3HgSQ8tfLX6hmWbqoB7ROYOXJ5577Oa
 RUY9utceY6xm3tYCQDTcJ6F0QFPq9d+oKhz/rMpljrPjqwYrS2WiSy/YG0e5TSSekGZW
 P2TQ==
X-Gm-Message-State: APjAAAWcyLgxlZbunU8Bcxyfww9F6eQugTpPqmbSrGuxnwXJ9Gs2DqFn
 q72M3Kzn721ckoPxL6t4oa7z3mtZIqHd+A==
X-Google-Smtp-Source: APXvYqy0FOCrZqPSltfgpBdt8o6xLozcCbwHBwRWFoaHn55bEjaJ8JTHvT5swtqFo1QOM67NGziH4Q==
X-Received: by 2002:a17:90a:2464:: with SMTP id
 h91mr35845162pje.9.1570463030334; 
 Mon, 07 Oct 2019 08:43:50 -0700 (PDT)
Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127])
 by smtp.gmail.com with ESMTPSA id k5sm20779345pfp.109.2019.10.07.08.43.49
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Mon, 07 Oct 2019 08:43:49 -0700 (PDT)
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon,  7 Oct 2019 08:43:38 -0700
Message-Id: <20191007154343.8556-1-stephen@networkplumber.org>
X-Mailer: git-send-email 2.20.1
In-Reply-To: <20190928003758.18489-1-stephen@networkplumber.org>
References: <20190928003758.18489-1-stephen@networkplumber.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: [dpdk-dev] [PATCH v5 0/5] mbuf copy/cloning enhancements
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

This patch set is all about improving the mbuf related cloning
and copying. They are motivated by seeing issues with mbuf copying
in rte_pdump and realized this a wider and more general problem.
The pdump copy could not handle different size pools and did
not handle meta data, etc.

They cause no functional or ABI changes. The only visible part
to older code is converting a couple of inlines to real functions.
This kind of change confuses checkpatch which thinks these new
functions should be marked experimental when they must not be.

v5 - add back the test (dropped by accident in v4)
v4 - common mbuf header fields copy routine
v3 - split linearize into internal/external
     copy private data in pktmbuf_copy
v2 - add pdump use of pktmbuf_copy
     fix version in map

Stephen Hemminger (5):
  mbuf: don't generate invalid mbuf in clone test
  mbuf: delinline rte_pktmbuf_linearize
  mbuf: deinline rte_pktmbuf_clone
  mbuf: add a pktmbuf copy routine
  mbuf: add pktmbuf copy test

 app/test/test_mbuf.c                 | 129 ++++++++++++++++++++++++
 lib/librte_mbuf/rte_mbuf.c           | 145 +++++++++++++++++++++++++++
 lib/librte_mbuf/rte_mbuf.h           | 127 +++++++++--------------
 lib/librte_mbuf/rte_mbuf_version.map |   8 ++
 4 files changed, 332 insertions(+), 77 deletions(-)

-- 
2.20.1