Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761407AbYA2E3o (ORCPT ); Mon, 28 Jan 2008 23:29:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755521AbYA2E3d (ORCPT ); Mon, 28 Jan 2008 23:29:33 -0500 Received: from mx2.suse.de ([195.135.220.15]:49958 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754906AbYA2E3c (ORCPT ); Mon, 28 Jan 2008 23:29:32 -0500 From: Andi Kleen To: Robert Hancock Subject: Re: DMA mapping on SCSI device? Date: Tue, 29 Jan 2008 05:28:00 +0100 User-Agent: KMail/1.9.1 Cc: linux-arch@vger.kernel.org, ide , linux-kernel , linux-scsi@vger.kernel.org References: <479E6E8C.2090501@shaw.ca> In-Reply-To: <479E6E8C.2090501@shaw.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801290528.00934.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1066 Lines: 24 > The ideal solution would be to do mapping against a different struct > device for each port, so that we could maintain the proper DMA mask for > each of them at all times. However I'm not sure if that's possible. I cannot imagine why it should be that difficult. The PCI subsystem could over a pci_clone_device() or similar function. For all complicated purposes (sysfs etc) the original device could be used, so it would be hopefully not that difficult. The alternative would be to add a new family of PCI mapping functions that take an explicit mask. Disadvantage would be changing all architectures, but on the other hand the interface could be phase in one by one (and nF4 primarily only works on x86 anyways) I suspect the later would be a little cleaner, although they don't make much difference. -Andi -- 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/