Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 30 Sep 2002 13:23:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 30 Sep 2002 13:23:40 -0400 Received: from [198.149.18.6] ([198.149.18.6]:23464 "EHLO tolkor.sgi.com") by vger.kernel.org with ESMTP id ; Mon, 30 Sep 2002 13:23:40 -0400 Date: Mon, 30 Sep 2002 20:43:20 -0400 From: Christoph Hellwig To: Ingo Molnar Cc: lord@sgi.com, Arjan van de Ven , cw@f00f.org, linux-kernel@vger.kernel.org, Linus Torvalds Subject: Re: [patch] smptimers, old BH removal, tq-cleanup, 2.5.39 Message-ID: <20020930204320.A21715@sgi.com> Mail-Followup-To: Christoph Hellwig , Ingo Molnar , lord@sgi.com, Arjan van de Ven , cw@f00f.org, linux-kernel@vger.kernel.org, Linus Torvalds References: <20020930194529.A15138@sgi.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 Mon, Sep 30, 2002 at 07:12:54PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 840 Lines: 19 On Mon, Sep 30, 2002 at 07:12:54PM +0200, Ingo Molnar wrote: > > Not exactly. All your work on one queue is internally serialize. An > > totally unserialized workqueue would be best for XFS. > > you can create as many queues as you wish - one per CPU for example. Or > one per mounted fs per CPU. Yeah. But adding a create_workqueue_per_cpu that has one queue and thead per cpu to which queue_work dispatches would centralize the code needed to manage that in one place instead of duplicating it over and over. Sure both works, but IMHO hiding it behind a nice abstraction is much better. - 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/