Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270384AbTHSOJz (ORCPT ); Tue, 19 Aug 2003 10:09:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270319AbTHSOJy (ORCPT ); Tue, 19 Aug 2003 10:09:54 -0400 Received: from zeus.kernel.org ([204.152.189.113]:11771 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id S270625AbTHSNd0 (ORCPT ); Tue, 19 Aug 2003 09:33:26 -0400 To: Alan Cox Cc: Pete Zaitcev , Krzysztof Halasa , Linux Kernel Mailing List Subject: Re: [PATCH] RFC: kills consistent_dma_mask References: <20030818111522.A12835@devserv.devel.redhat.com> <1061298438.30566.29.camel@dhcp23.swansea.linux.org.uk> From: Jes Sorensen Date: 19 Aug 2003 09:20:34 -0400 In-Reply-To: <1061298438.30566.29.camel@dhcp23.swansea.linux.org.uk> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 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: 1102 Lines: 20 >>>>> "Alan" == Alan Cox writes: Alan> On Maw, 2003-08-19 at 10:03, Jes Sorensen wrote: >> That would be totally messy. Having drivers do the accounting of >> what mask is currently set and have them switch back and forth >> depending on what type of allocation is currently being used would >> be a nightmare to debug. Alan> It is messy, but the consistent mask only helps a small subset Alan> of cases. Having an __pci_alloc_foo that took the mask as an Alan> argument is (a) trivial (b) adds almost no code (c) solves the Alan> general case problem. And d) puts the accounting back into the drivers in duplicate. So far we have managed pretty well with the distinction between consistent and dynamic, but sure if there is hardware out there where it makes sense to have a more generic interface we should consider it. Jes - 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/