From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id B3C6537A6 for ; Wed, 19 Apr 2017 14:27:53 +0200 (CEST) Received: by mail-wm0-f44.google.com with SMTP id w64so78977345wma.0 for ; Wed, 19 Apr 2017 05:27:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=WPE6BgyK0iYTe7dc5WN+WjNJxUsWcvgMD2grpqBOkrU=; b=g+jCqwvCJtaSz6evcGPcz+s3NGaTy/3J5zl7Mxa0PZHWPSOnbKPxMmQckDoo3QRO9T edYCrv1xBl6d+vBT27MR3q2AydlpJ9RETN+87rZoM1GKpeIlSIacsOKirqLza5ivroYB g/GSp8YZUqXo1K2fgk0vVnlDLGmAxpui30nNSly+4xMw1HIIenct9ceHFs4qvY2c1xnB DvX7JUuFrBcYmRWqApp6nTo8JJQpB+w2l8GO9nmJh3paq6zftsl3/2dH4kOw/kdqGtLS qKv6t9pIoiItEQi4T8MIyRnoce9BLpRe3HkBzRiCtVIXQ1Ms1mmvtrHWhSYiitjR1W1k rGBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=WPE6BgyK0iYTe7dc5WN+WjNJxUsWcvgMD2grpqBOkrU=; b=PD8QEU5Br3TU64teXHLq2mg8hgdtAt8sooF9PbzhJPh2CghFN6hquSl+ng9Mtml50N BYG6wPTe4dSVwQK7aBsvzkqYBFSji+TWHp+yX/MlBK7NyusZCWba+UlIKffRHnLysd/f HR1J9h3P7wt/L1vYzDPzTc5yZZ1th9etOA1JEruFbxiQe77gbBBCtsvqb1R7vHhWAVHc sXYoFpMFptNmf0adAI1Cqrq+mI+20hB5HlwhfQiKsT5R6zraYS+O6aQm2J5PAfHp0VXs kZPzn4vBwGbVSTLx335DJ35imidJik4h6TUKXW0JbeN0mkEihlv98ogJdKtedXoxOoJT n41Q== X-Gm-Message-State: AN3rC/5fJ64mRu5bwYjjh+DGd1j/P5IlM5lFzK5+cZQSFPTggBnkEhYR bLUmaLODlqnQJuXHJvo= X-Received: by 10.28.138.209 with SMTP id m200mr2666318wmd.109.1492604873162; Wed, 19 Apr 2017 05:27:53 -0700 (PDT) Received: from glumotte.dev.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id n6sm3128555wrb.62.2017.04.19.05.27.53 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 19 Apr 2017 05:27:53 -0700 (PDT) Date: Wed, 19 Apr 2017 14:28:20 +0200 From: Olivier MATZ To: Thomas Monjalon Cc: dev@dpdk.org Message-ID: <20170419142820.5902a513@glumotte.dev.6wind.com> In-Reply-To: <4815628.Qayg3alc5T@xps> References: <1488966121-22853-1-git-send-email-olivier.matz@6wind.com> <2ead9890-5759-5c31-1805-588967c7cbf2@intel.com> <20170418150448.49b9934f@glumotte.dev.6wind.com> <4815628.Qayg3alc5T@xps> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:27:53 -0000 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?