From owner-freebsd-threads@FreeBSD.ORG Mon Apr 23 06:56:03 2012 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C1055106566C for ; Mon, 23 Apr 2012 06:56:03 +0000 (UTC) (envelope-from yfw.bsd@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 89F3C8FC15 for ; Mon, 23 Apr 2012 06:56:03 +0000 (UTC) Received: by obqv19 with SMTP id v19so17465213obq.13 for ; Sun, 22 Apr 2012 23:56:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=MFCw7DAWBYtbw+J4oXzrbt787AC6kyklN7A1sGodMNM=; b=b87ZjzG8mFHLrbct5sMtJirUI9kdvMEt56LgjncyYuUUmwsA3TcyMzeaux4okn/Fii 8P8U4SV2JJAW9SDQYtHdl4/hhxiimVFT/xShhtMsgLO9JueSGkelI4IXqxPhJn7lPyUg eZWvnXtL4z5l47F9xOdpvOh03lVUtkZ7apW4Ays2RsIm2sggye61q0Wo0cKJEwaqf7IT c0yxY+0gIhPZYnAZHIrgErcYne3Dt6WLT2YR3SF0U4RBA1TuwjibQgYsgJRxG0n/9MNZ gI/0FEKmAATDP5XGYX+YrLJW7/H8ZOaBk7pkc2Z9vmPtpl/9ZgbORC0s8uUkqLjirX1B iekw== MIME-Version: 1.0 Received: by 10.182.232.38 with SMTP id tl6mr5975973obc.16.1335164163204; Sun, 22 Apr 2012 23:56:03 -0700 (PDT) Received: by 10.60.125.135 with HTTP; Sun, 22 Apr 2012 23:56:03 -0700 (PDT) Date: Mon, 23 Apr 2012 14:56:03 +0800 Message-ID: From: Fengwei yin To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: jack.ren@intel.com Subject: About the memory barrier in BSD libc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2012 06:56:03 -0000 Hi list, If this is not correct question on the list, please let me know and sorry for noise. I have a question regarding the BSD libc for SMP arch. I didn't see memory barrier used in libc. How can we make sure it's safe on SMP arch? BTW, there are memory barrier used in kernel instead. So I suppose the memory barrier is needed. Regards Yin, Fengwei