From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 6A08969FC for ; Fri, 13 Jan 2017 16:32:37 +0100 (CET) Received: by mail-wm0-f46.google.com with SMTP id r126so70042200wmr.0 for ; Fri, 13 Jan 2017 07:32:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=p4yegVGZHxfr7ZY9jt7DZ/P4XDN9rhP5AtHSoPPDJYM=; b=ydqbg3ks/2sKtrwjQ5EMwHkAQFBd8pxmel9XdANFJizXMYAqu0ZHddrRDiaz4uhwqP LcPHfimy2dOZsiqaUiNIRFc53EKfsmCXx3DWtG+OOKhLKCgqslbHMxiqntbzk6rQrqVY WXJyfb6NRUeQ/z4UcgBhCPLBjmJlyJsP4ujpsAZyGh0hFHSj160/UHSywHRX/8ycjMPC tarWaOmglwXU3n8MkqVM8z09lGxUNgvPKY7tr/zoleXTyx3AN7n/8n+0nKYPhsJNb4Sk iKOvfOy8AQODzvlp67DFoG0LKxut9olxyWDgAHXWPvMIBCEbivXOpwcEtIXRaG3+V07j HWQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=p4yegVGZHxfr7ZY9jt7DZ/P4XDN9rhP5AtHSoPPDJYM=; b=XKe3nwqJI4ZYRzOS2svTbfO7GlFKnkHEuILB79wDTDqBRuiFnsYdlTwFFhJlEHlqxw Xi0DbRotxjt20SemVyCc3zpxvQ5YPFwKEqOAE9CyP1RBWnPOqhH2SO/Whu7CZfUaYk6T XgB6N5lD17Xq52FHb6GVGaflCtOL9k3xcYadf/DJdD/tFqIKYiWnQzv4kwATYQNVteE4 oxgQO/oHT5E42jN7rDjTO6G4WXrlVKygAVLAXNSFMYBAVzF16wBvG2AXstwP3rZmZDjP LlfI+9v7lrbEk8WV/7CNeqbXhVerBUD8hH9x62QWPwE7QIG92Im2HKVMV7a7zeOCwL6y ofTA== X-Gm-Message-State: AIkVDXL7SS1dtq+LTI+A/owU8cRNFm6O108nBrIJmIzwDeabSM64rRUzLk6yoiPja9AdcQLB X-Received: by 10.28.228.87 with SMTP id b84mr2722741wmh.0.1484321557154; Fri, 13 Jan 2017 07:32:37 -0800 (PST) Received: from platinum (2a01cb0c03c651000226b0fffeed02fc.ipv6.abo.wanadoo.fr. [2a01:cb0c:3c6:5100:226:b0ff:feed:2fc]) by smtp.gmail.com with ESMTPSA id e5sm5009250wma.12.2017.01.13.07.32.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 13 Jan 2017 07:32:37 -0800 (PST) Date: Fri, 13 Jan 2017 16:32:34 +0100 From: Olivier Matz To: Tomasz Kulasek Cc: dev@dpdk.org, Pablo de Lara Message-ID: <20170113163234.1f38b9ee@platinum> In-Reply-To: <1484214044-9432-1-git-send-email-tomaszx.kulasek@intel.com> References: <1483634640-33892-1-git-send-email-tomaszx.kulasek@intel.com> <1484214044-9432-1-git-send-email-tomaszx.kulasek@intel.com> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v5] mbuf: add a function to linearize a packet 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: , X-List-Received-Date: Fri, 13 Jan 2017 15:32:37 -0000 On Thu, 12 Jan 2017 10:40:44 +0100, Tomasz Kulasek wrote: > This patch adds function rte_pktmbuf_linearize to let crypto PMD > coalesce chained mbuf before crypto operation and extend their > capabilities to support segmented mbufs when device cannot handle > them natively. > > Included unit tests for rte_pktmbuf_linearize functionality: > > 1) Creates banch of segmented mbufs with different size and number of > segments. > 2) Fills noncontigouos mbuf with sequential values. > 3) Uses rte_pktmbuf_linearize to coalesce segmented buffer into one > contiguous. > 4) Verifies data in linearized buffer. > > Dependencies: > > This patch is rebased to the dpdk-next-crypto and should be applied > before "Chained Mbufs support in SW PMDs" patchset. > > changes in v5: > - name of patch changed, > - improved coding style, > > changes in v4: > - separated from "Chained Mbufs support in SW PMDs" patch set for > better reviewing, > - merged "rte_pktmbuf_linearize" implementation with unit tests, > > changes in v3: > - rebased to dpdk-next-crypto > > changes in v2: > - rte_pktmbuf_coalesce replaced with rte_pktmbuf_linearize > > Cc: Pablo de Lara > Cc: Olivier Matz > Signed-off-by: Tomasz Kulasek Acked-by: Olivier Matz Just one comment about the changelog for next time: as it's not something we need to keep in the git history, you can put it after the '---', so it will be dropped when applying the patch with 'git am'. Thanks, Olivier