From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 25 Sep 2002 13:37:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 25 Sep 2002 13:37:18 -0400 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:34856 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Wed, 25 Sep 2002 13:37:18 -0400 Date: Wed, 25 Sep 2002 13:42:15 -0400 From: Pete Zaitcev To: Ingo Molnar Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org Subject: Re: cmpxchg in 2.5.38 Message-ID: <20020925134215.A17831@devserv.devel.redhat.com> References: <20020925120725.A23559@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from mingo@elte.hu on Wed, Sep 25, 2002 at 10:26:34AM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org OK, I'll work around the cmpxchg locally. But for the record, I am concerned with the API inflation instigated by the single source. The scheduler-specific bitmaps were bad enough, even though Bill Irvin showed a better way to do it at the time. Now, the same gentleman invents one more API. I may be getting senile, though. -- Pete