From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wj0-f169.google.com (mail-wj0-f169.google.com [209.85.210.169]) by dpdk.org (Postfix) with ESMTP id 32D475598 for ; Thu, 1 Dec 2016 17:26:21 +0100 (CET) Received: by mail-wj0-f169.google.com with SMTP id v7so209144472wjy.2 for ; Thu, 01 Dec 2016 08:26:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=yjWKs4xtNurHqze8pS05IHqaImLE2CVOGfkHwNd8uyc=; b=tAP5eviCRLx+VQmjyHow+8XoQuvMxIPQH/g6HlwKRnuGtYD04kpG10osm7lsg/5wpz F4eBUwE5KOknvcOhGbrXP8fFToyw26Itj6lQc9Fim+bjrqFO5GO47Y/IyqTRuDrUD4Vw FVTAFB51AaU+CPuqzQXNBdp78JxyqTnhon+BKooGwn2+x8q3b3AP2BrkjKe+hg3FVw8n UUc2EhwkWB8A1Mg1miFDv10b2aa+I5CpTjtuCP14twQcrSgVuWl3zwnxSK2fbqFSVZpC RR9ua1BiuBjGV7x8NHTCg8Tm9BUXP8zYl1tgoQhJIQQjtHtPvIrBKp2fbKEJHwB6bZo4 n7Zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=yjWKs4xtNurHqze8pS05IHqaImLE2CVOGfkHwNd8uyc=; b=GASMbkcdrv1HncNAloEDkUgAvUlRKetCXBNZ2tpEfcc3clChVPFwV4umvkRaHUuSNw 78nmh9e2vjZFkQOiAJCs7QJAnOnsa7vWgoGq+sfvUQada9EYJhPg0h0ZNxPXfaUSYCnE tOqC9NBweWdSgYUvZSTXwpq5Ra06s00J4WmGInY9mpRvWYj5HQpTMGXNeuFbZyuXTL8Z LojXKtCq/MtfihP7VlpYkCrAqJLu68yr5mOXhUJTeLBWrVpAnrUJi/Dqum5Hg0MXjStw IM6uwvAE0X6N0DXRttP43FSzCB5YfxI3mp+k9aMGG3EIJdHX+Bga4N4ckRedR+tWd8E4 kscw== X-Gm-Message-State: AKaTC03Ss9o6TH/8jXKA5+MqL00Zo8nKG6Mt1iKZlUm2dFpozNuzRjG96rhWCGZe+1w8gmkv X-Received: by 10.194.14.73 with SMTP id n9mr37742416wjc.189.1480609580867; Thu, 01 Dec 2016 08:26:20 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id c133sm1677984wme.12.2016.12.01.08.26.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Dec 2016 08:26:19 -0800 (PST) From: Thomas Monjalon To: Tomasz Kulasek Cc: dev@dpdk.org, konstantin.ananyev@intel.com, olivier.matz@6wind.com Date: Thu, 01 Dec 2016 17:26:18 +0100 Message-ID: <6019452.hetlqJUqAU@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1479922585-8640-2-git-send-email-tomaszx.kulasek@intel.com> References: <1477486575-25148-1-git-send-email-tomaszx.kulasek@intel.com> <1479922585-8640-1-git-send-email-tomaszx.kulasek@intel.com> <1479922585-8640-2-git-send-email-tomaszx.kulasek@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v12 1/6] ethdev: add Tx preparation 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: Thu, 01 Dec 2016 16:26:21 -0000 2016-11-23 18:36, Tomasz Kulasek: > Added fields to the `struct rte_eth_desc_lim`: > > uint16_t nb_seg_max; > /**< Max number of segments per whole packet. */ > > uint16_t nb_mtu_seg_max; > /**< Max number of segments per one MTU */ How (and when) an application is supposed to use these fields? Is it useful to expose them if we make tx_prepare() mandatory?