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 F2EF05587 for ; Wed, 19 Apr 2017 14:56:20 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6B4AB2081F; Wed, 19 Apr 2017 08:56:20 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 19 Apr 2017 08:56:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc: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=xtNMIbZKRYv5wvy IrI6FZdjwyLY4QvphiDcKGDFsoMI=; b=PuIW+AwR6gSfNbqlWDZ9bScW6U/g9QF oicfnKbacjXdcjNs+iL2FzYn+q1V7SHipQP+rhuJ/Wujkwa2zD0pifhRyBjhj8eU UtNAxY+q0UCqz+5HeEcc3vR8xLXga3Df4MTgNEi7oM4on+5NQOkVzd2KbgcsCQih eURd4M0Dtg0o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=xtNMIbZKRYv5wvyIrI6FZdjwyLY4QvphiDcKGDFsoMI=; b=e/dBp2nV cMB/mabLWBrpi8KUvlGsI9fSrLw2iMN26nwgLSO11XoVteiLF4BVtvp1C+nwS0nH Zj1XP0Ppwp/n79XYXm76383shhUcjAMuChKBjZJGnK++DGus1oxPziA3B9R6y5xJ 8wzE6oNeIvOzoyi2+uK2EBP5codnGVkJycsGKrZNOxmmLOR9+f0+Ytu6asrEsNJX hdeyfKjmImOGaXjpkRxy35Ebg8o4qSgdC6gakzBxvto6N4sxiwWnr5jDODuKq93j +AFDFt7fP0heAFA5pV/IoulbSkM0+v8LvSIrMum8Ic8TWWvTmOi2+wJmTMppq09d JMSBiw30BQgJNg== X-ME-Sender: X-Sasl-enc: HezLx21nSyW87m9Ibnk7AZqKHOz5QKiApiaNl4DyAqbR 1492606579 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id E1A427E0EE; Wed, 19 Apr 2017 08:56:19 -0400 (EDT) From: Thomas Monjalon To: Olivier MATZ Cc: dev@dpdk.org, ferruh.yigit@intel.com Date: Wed, 19 Apr 2017 14:56:19 +0200 Message-ID: <2313944.lXlCutk7ET@xps> In-Reply-To: <20170419142820.5902a513@glumotte.dev.6wind.com> References: <1488966121-22853-1-git-send-email-olivier.matz@6wind.com> <4815628.Qayg3alc5T@xps> <20170419142820.5902a513@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 12:56:21 -0000 19/04/2017 14:28, Olivier MATZ: > On Wed, 19 Apr 2017 11:39:01 +0200, Thomas Monjalon wrote: > > 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). > > I agree here. > > > 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. > > Who is the "we"? In that particular case, is it my job? > Shouldn't we notify the PMD maintainers more precisely? We as a community :) I think Ferruh will lead the follow-up of this rework, as next-net maintainer.