Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272799AbTG3Hkv (ORCPT ); Wed, 30 Jul 2003 03:40:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272802AbTG3Hku (ORCPT ); Wed, 30 Jul 2003 03:40:50 -0400 Received: from mx1.elte.hu ([157.181.1.137]:51884 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S272799AbTG3Hkt (ORCPT ); Wed, 30 Jul 2003 03:40:49 -0400 Date: Wed, 30 Jul 2003 09:40:14 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Andrea Arcangeli Cc: Andrew Morton , , Subject: Re: PATCH: Race in 2.6.0-test2 timer code In-Reply-To: <20030730073458.GA23835@dualathlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 696 Lines: 18 On Wed, 30 Jul 2003, Andrea Arcangeli wrote: > [...] I'd feel much safer with the whole timer API being smp safe w/o > requiring driver developers to add complicated external brainer locking. > This will provide a much more friendly abstraction. i agree with the goal, but your patch does not achieve this. Your patch does not make double-add_timer() safe for example. As far as i can see your 2.6 patch only introduces additional overhead. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/