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 3245B58CD for ; Wed, 19 Apr 2017 15:12:04 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id DDEDD20C1B; Wed, 19 Apr 2017 09:12:03 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 19 Apr 2017 09:12:03 -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=FgQCKy4XmxSALu+ F3ZpRZE1AfwROIqLxFuj/kpRV04o=; b=JJDn2q547/GURZIq4nuuVfL44ZdnxAE 5QPCplMRckdq8gkwuW6fvGOxqXAm/3SiruQEp6bW9jMRoV5PqvboXdW4tPsU5F0L ajRJcImKU+KKjxEpQJdPCes9TG7agyy0lFenhutbML5VDDTIwXEVh68qdwWRW+LP P8HuFbylmwFs= 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=FgQCKy4XmxSALu+F3ZpRZE1AfwROIqLxFuj/kpRV04o=; b=XyyLHYna QX9LIKNYtlH9SHJ7oAieutzZTkz6IqhUo+XMAR6K5IxoMe+BqJRbv3n951KsvGOr FeARwQKZUyhF1gBXebkyJd06akmW2N9O2DWV3o3LO6mJUJgX/SQV9BobcflOCpQJ pns76RS1iq767WBReF0+MPLGqIX88ZAxCQTkQ6sEZl8SFx1ThLLWUd4O4gC3OZuC UU2+6YVX6dIvzlGfCd6txZjoPaX/jeQJ/p6OhhodUpxhm9SK8QfuzoNB3wsSG59l jtlj1SaWVjT3GT2mynpVEDXDXMOXaOEycGvuYam+HU/1Mq7h+dghxXvkd+U/5Nns W77XxaWcdc+Nag== X-ME-Sender: X-Sasl-enc: aarRFhin4/andvpNcWMmIXfOMCpxh3vHp0hTRXXcrAfR 1492607523 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8AA93246FC; Wed, 19 Apr 2017 09:12:03 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: Olivier MATZ , dev@dpdk.org Date: Wed, 19 Apr 2017 15:12:02 +0200 Message-ID: <5143340.QmOeufPag9@xps> In-Reply-To: <9e68c252-4ce0-18f5-f054-394c0e067054@intel.com> References: <1488966121-22853-1-git-send-email-olivier.matz@6wind.com> <2313944.lXlCutk7ET@xps> <9e68c252-4ce0-18f5-f054-394c0e067054@intel.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 13:12:04 -0000 19/04/2017 15:03, Ferruh Yigit: > On 4/19/2017 1:56 PM, Thomas Monjalon wrote: > > 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. > > I can trace net PMDs. > > Lets start in dev mail list and make sure what a PMD maintainer should > do is clear, we can wait for a release for updates, later I can ping > missing ones individually, what do you think? Sounds like a plan :) Thank you Ferruh and Olivier