From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id CE3B9A48C for ; Mon, 22 Jan 2018 22:00:18 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 35F3521333; Mon, 22 Jan 2018 16:00:18 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 22 Jan 2018 16:00:18 -0500 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; s=mesmtp; bh=FuqHudJ4NBdJRWH14u+KUPIFsl 361oPMQFH9jIrOm3Y=; b=AFmdxg91+gztRCwCx4VywwY4MPcehSmatFpf/15WVs hiPnK6EqGsQe3uVDOjFV8fPa2gjnE34EGAs4G6myIq7u70LY6EwbnfCTA5o2rt5D MU4r0rGYKgOqBOxGA3x18FrljHcgDciKvAjLJ830gtsocJEU7p1ykDgT+riEcNmn g= 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; s=fm1; bh=FuqHud J4NBdJRWH14u+KUPIFsl361oPMQFH9jIrOm3Y=; b=SvK6I3FGx2eU5dTbDWfX2V YLCTs3FDXywB4IHOnQPoHPM5vhz4wj7UoHEnbQ9JfhduZGUzCnX3F9siSrQGiX6L nVCHQgy8ZMumKpYwHEb42Zh+nVS0j7WXGP7ndB91JGdVqzqgMHiIlmWj1bHPbFiq uZrS68VLVl0Xpa4/113OflydcX2Pxcqc6bjqKhlHblYwOvY71yjxjJsFwgm0KfUG AmdPK0V/Mt0Xn/nctSUZTRvEk4dGiXPrzZ5DiV49a6TVoZTqEbqZRkyPH58gxcYQ TG57FBKyH8aK5Rrl5WLiamyT+SxXvlVsXIxU4CJtxmCh7s6sumHTyhqiV0GDyUJw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CAB0424547; Mon, 22 Jan 2018 16:00:17 -0500 (EST) From: Thomas Monjalon To: Yongseok Koh , Andrew Rybchenko Cc: dev@dpdk.org, "jianbo.liu@arm.com" , Jerin Jacob , Adrien Mazarguil , =?ISO-8859-1?Q?N=E9lio?= Laranjeiro , "bruce.richardson@intel.com" , "Ananyev, Konstantin" , Chao Zhu Date: Mon, 22 Jan 2018 21:59:39 +0100 Message-ID: <1785374.EvMsrt8sou@xps> In-Reply-To: <5B266F6C-A33B-4019-BFDE-9CAC80835200@mellanox.com> References: <20180116011050.18866-1-yskoh@mellanox.com> <805e1578-6e4d-6a1b-00ce-13e3b1c16be8@solarflare.com> <5B266F6C-A33B-4019-BFDE-9CAC80835200@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 1/8] eal: introduce DMA memory barriers 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: Mon, 22 Jan 2018 21:00:19 -0000 22/01/2018 19:29, Yongseok Koh: > > On Jan 18, 2018, at 11:16 PM, Andrew Rybchenko wrote: > > Maybe it would be useful to: > > - avoid duplication of so long explanations (put in in one place and add reference?) > > May have to ask Thomas how to do this. Thomas? You can group barriers by type (SMP, IO, DMA) with this doxygen syntax: https://www.stack.nl/~dimitri/doxygen/manual/grouping.html#memgroup So you can have a common description of the group, plus a description of each function.