From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261218AbULRTjl (ORCPT ); Sat, 18 Dec 2004 14:39:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261223AbULRTjl (ORCPT ); Sat, 18 Dec 2004 14:39:41 -0500 Received: from users.ccur.com ([208.248.32.211]:57454 "EHLO gamx.iccur.com") by vger.kernel.org with ESMTP id S261218AbULRTjk (ORCPT ); Sat, 18 Dec 2004 14:39:40 -0500 Date: Sat, 18 Dec 2004 14:39:39 -0500 From: Joe Korty To: Joseph Seigh Cc: linux-kernel@vger.kernel.org Subject: Re: What does atomic_read actually do? Message-ID: <20041218193939.GA23080@tsunami.ccur.com> Reply-To: joe.korty@ccur.com References: <1103394867.4127.18.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 18, 2004 at 02:20:44PM -0500, Joseph Seigh wrote: > so why use atomic_read? Because atomic_t is opaque and atomic_read lets you get at the value when that is all you want to do. Regards, Joe