From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 1/3] mem: provide thread-unsafe contig walk variant Date: Fri, 13 Jul 2018 11:21:04 +0200 Message-ID: <4613648.bFHoFLOs9j@xps> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Anatoly Burakov Return-path: Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id EB2AA4C9D for ; Fri, 13 Jul 2018 11:21:07 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 12/06/2018 11:46, Anatoly Burakov: > Sometimes, user code needs to walk memseg list while being inside > a memory-related callback. Rather than making everyone copy around > the same iteration code and depending on DPDK internals, provide an > official way to do memseg_contig_walk() inside callbacks. > > Signed-off-by: Anatoly Burakov Series applied, thanks