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 42641A56E for ; Fri, 19 Jan 2018 00:53:04 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CC630209B1; Thu, 18 Jan 2018 18:53:03 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 18 Jan 2018 18:53:03 -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=tLl56MMm7abOJsZxmxHyklvLtS 3bOMcU7yTV/3OSgEQ=; b=NfXfK7o45uD1ceU/fRhz/iTI1NvKRxtoBVLQqBVzqW izyz5fR2mZWGyiDg0Rgy3iKmWHDQw8ahSxPYnIAsYAL39bwrfJ2VU9tz8CG2PrwT UOOsU4So/u4tTnpeXoyOP1yppvqAy3hFhWqJHEwd9P5fLriMS8Gvt2LNWxtcqZdU 8= 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=tLl56M Mm7abOJsZxmxHyklvLtS3bOMcU7yTV/3OSgEQ=; b=QZVBgbO2Iu5gTyE8T2zjE/ ms35hlYmKWf73zu/ZAKjrGxgM9Sw3YrzbAMTLhwWNUHRLyangohVKPgL/R9byj5g hW8FixWX3mvU1sfo8mH1v7iTUnx4F4yvXstDmeFWm7TJqVtETnC4c/YsrCbINyt2 3guStUFKIkuReIaRGFIVXExazBAVTtPQs3JtuEijpP3CIfWQhmDExvc6QoaYM0Pr oE3yMXzdv6gKBOHtDTYNF4WY0PJaIjFB+YIZ6LoSrAtlZDKYIG3JL94PVE+XQXbs 2DrcPHTsIp35uSGZ8brSyFpvUhVGbZvqIOd9c+kdcajJS3G6jN47DO6MJbdSnO/A == 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 77C6F7E1A2; Thu, 18 Jan 2018 18:53:03 -0500 (EST) From: Thomas Monjalon To: Jia He , Jia He Cc: dev@dpdk.org, Jerin Jacob , Jianbo Liu , Jan Viktorin , Olivier Matz , konstantin.ananyev@intel.com, hemant.agrawal@nxp.com Date: Fri, 19 Jan 2018 00:52:29 +0100 Message-ID: <1629453.JGSeBPTEmg@xps> In-Reply-To: <3399617.YsM4r4Ydhj@xps> References: <1516161831-28719-1-git-send-email-hejianet@gmail.com> <23810751-921d-4e3a-bac6-95d251cc122f@gmail.com> <3399617.YsM4r4Ydhj@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v8 3/3] ring: introduce new header file to support C11 memory model 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: Thu, 18 Jan 2018 23:53:04 -0000 17/01/2018 10:09, Thomas Monjalon: > 17/01/2018 09:47, Jia He: > > > > Hi Thomas > > > > On 1/17/2018 4:24 PM, Thomas Monjalon Wrote: > > > 17/01/2018 05:03, Jia He: > > >> To support C11 memory model barrier, 2 options are suggested by Jerin: > > >> 1. use rte_smp_rmb > > >> 2. use load_acquire/store_release(refer to [1]). > > >> CONFIG_RTE_RING_USE_C11_MEM_MODEL is provided, and by default it is "n" > > >> on any architectures so far. > > > In previous patches, it was enabled for ARM. > > > You decided to not enable it at all? > > Sorry, maybe I misunderstand your previous mail. > > >This config option should be added in the common file (as disabled). > > Do you mean CONFIG_RTE_RING_USE_C11_MEM_MODEL=n in comm_base and > > "y" in armv8 config? > > Yes, exactly Please, could you send a v9? Thanks