From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id D8D832B9D for ; Wed, 20 Jul 2016 17:01:13 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id o80so73311146wme.1 for ; Wed, 20 Jul 2016 08:01:13 -0700 (PDT) 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=QTXrDfly8t+DGu7aDUgmJ3UP0ZV8Oy5eAiA69Pw5NWs=; b=Hh9cE1HnErTIxIdbvzbutT/6SGisp21rfAJ/nmWk2dsyMFpvA9cu/wCCI/FsAmfXl3 g1DqcbFUHGH/7ahXho98kmYZOhoRWgUUkrTO1p7ylNVaTot8sWmWlOLdTc4MxS0/E9IZ L0SSUeEYKKV296VwczfGJe3vIAg1DpP2yE2LT7sWyRnbwQME14dr0/G7keP8rLKgqkFr qHtyvSeGcanzMKQ6Gcc/Qo7g2nKw5w2bw9ltXihk7LbmuKkhq2hGAM68VIIsSPtrjyJO xqA38U+2W7KCR35zS8I7GPdkl0SPZ0VRj2foJkCUHz/io7HMFPY35C8q53BI/slnsoJw fNGQ== 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=QTXrDfly8t+DGu7aDUgmJ3UP0ZV8Oy5eAiA69Pw5NWs=; b=jW+4rEG0oxOdX1N5ZaLvRFScLmLSgh9D3ePw7CtQHih5z34LpNFk0quJUm1iNpDC8T u5FfFIqf4x44xjZHwqZ9+Ma1SdsXVU9XDqzD9aVk6LTSst3aQeZNvQ8Zo1BoLOHbUeWY yvpsack8f9TF9FyXlPolcccBNAdP4A8/73libz//iP8TOhDAFbqkdvGWfPB6fb9D5wkO cpxlgHoxJu1nVxguWrTOet47fW3EcPe5iIL+hxZQaDTEXGDBaV2V9dMDyXxZU9umoaNC sOyqIrzJ4uca4yxSPA0YFf3lmnun++UrrPfWjL1NkOuK387U5hv1E1RKQIM0tETBIlGT XSZg== X-Gm-Message-State: ALyK8tKVoe5YavZ2vF7NE6Ho6yCwxaovB4DfGhZs51ZCo2JvHZbuh64b3svh1//cz+RVkbku X-Received: by 10.194.234.198 with SMTP id ug6mr1761416wjc.76.1469026873623; Wed, 20 Jul 2016 08:01:13 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id b5sm1690143wjw.3.2016.07.20.08.01.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 08:01:12 -0700 (PDT) From: Thomas Monjalon To: Tomasz Kulasek Cc: dev@dpdk.org Date: Wed, 20 Jul 2016 17:01:11 +0200 Message-ID: <2192482.DY91PqGyRQ@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1469024691-58750-1-git-send-email-tomaszx.kulasek@intel.com> References: <1469024691-58750-1-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] doc: announce ABI change for rte_eth_dev structure X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 15:01:14 -0000 Hi, This patch announces an interesting change in the DPDK design. 2016-07-20 16:24, Tomasz Kulasek: > This is an ABI deprecation notice for DPDK 16.11 in librte_ether about > changes in rte_eth_dev and rte_eth_desc_lim structures. > > In 16.11, we plan to introduce rte_eth_tx_prep() function to do > necessary preparations of packet burst to be safely transmitted on > device for desired HW offloads (set/reset checksum field according to > the hardware requirements) and check HW constraints (number of segments > per packet, etc). > > While the limitations and requirements may differ for devices, it > requires to extend rte_eth_dev structure with new function pointer > "tx_pkt_prep" which can be implemented in the driver to prepare and > verify packets, in devices specific way, before burst, what should to > prevent application to send malformed packets. > > Also new fields will be introduced in rte_eth_desc_lim: nb_seg_max and > nb_mtu_seg_max, providing an information about max segments in TSO and > non TSO packets acceptable by device. We cannot acknowledge such notice without a prior design discussion. Please explain why you plan to work on this change and give a draft of the new structures (a RFC patch would be ideal). Thanks