From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 8CA5A37A6 for ; Wed, 19 Apr 2017 11:39:03 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 03A082090D; Wed, 19 Apr 2017 05:39:03 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 19 Apr 2017 05:39:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=0Too22xCRaZSj1t tEkByMDxvo21cziGHNACi4cMwkJE=; b=X4immSLTd0zB+x9y6lDEHm4KCj1k3Jz 8eEIu26yk5UQ9erPEVn7N11HnaTIwHV2f3MM6BAWVkgqxxqSBLCECPxLt1LEPWk+ X7fBt/pAAxWTYDucZX9xI/VcQyr5hx0ZtJbDubiaoCVgtGBUDjxhuv6OqOMRNMTq iJXV8XR9vlyA= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=0Too22xCRaZSj1ttEkByMDxvo21cziGHNACi4cMwkJE=; b=HwjW60PX +sx8atJ6B7sT2Hnz838j882Mj9aqG8Bc0NmbwCiZ9CP6ZeWcBLOM+M35X/ty3O9x L2S/ZpeNT9sj6EaRrG1sUX5u5e0x50krZGkAntuV4zdqiJW1ar4qZ6dmMJZZsF3W yQEqao1AL+At12w9Kp6bJ0hvt6DD1eQCggY3eHma1LnJKrS1daPYs8V6Do3CLp0M 2PQ/sRh5o1qj1kjX2608VuDPWGVVxwng7wF4QAc2IRcBiiye5fzHKOBWQ6OZAmP1 1mlD3Vx826iEPWhzJkTeCPqdBJ7h91w6EnHTcDZMI+jVm8VuCmExpsJh0qSloBGo aku1rbO3VqWtCg== X-ME-Sender: X-Sasl-enc: dOh2E1pdE+jqn6dyJFzaahqFTno3PLqeTT7+hMiriQll 1492594742 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9B164241E1 for ; Wed, 19 Apr 2017 05:39:02 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Date: Wed, 19 Apr 2017 11:39:01 +0200 Message-ID: <4815628.Qayg3alc5T@xps> In-Reply-To: <20170418150448.49b9934f@glumotte.dev.6wind.com> References: <1488966121-22853-1-git-send-email-olivier.matz@6wind.com> <2ead9890-5759-5c31-1805-588967c7cbf2@intel.com> <20170418150448.49b9934f@glumotte.dev.6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/8] mbuf: structure reorganization 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: Wed, 19 Apr 2017 09:39:03 -0000 18/04/2017 15:04, Olivier MATZ: > On Fri, 14 Apr 2017 14:10:33 +0100, Ferruh Yigit wrote: > > > 2017-04-04 18:27, Olivier Matz: > > >> Once this patchset is pushed, the Rx path of drivers could be optimized > > >> a bit, by removing writes to m->next, m->nb_segs and m->refcnt. The > > >> patch 4/8 gives an idea of what could be done. > > > > Hi Olivier, > > > > Some driver patches already received for this update, but not all yet. > > > > Can you please describe what changes are required in PMDs after this > > patch? And what will be effect of doing changes or not? > > Yes, I will do it. > > > Later we can circulate this information through the PMD maintainers to > > be sure proper updates done. > > That would be good. > > Do you know what will be the procedure to inform the PMD maintainers? > Is there a specific mailing list? We should explain the required changes on dev@dpdk.org as it can be interesting for a lot of people (not only current maintainers). Then we just have to make sure that the PMDs are updated accordingly in a good timeframe (1 or 2 releases). If we feel someone miss an important message, we can ping him directly, without dev@dpdk.org cc'ed to make sure it pops up in his inbox. The other communication channel to ping people is IRC freenode #dpdk.