PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
Sorry dropped l-k cc by mistake
From: Andi Kleen <[email protected]>
To: Jens Axboe <[email protected]>
Subject: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
Date: Thu, 2 Mar 2006 13:16:37 +0100
User-Agent: KMail/1.9.1
Cc: Michael Monnerie <[email protected]>,
Jeff Garzik <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[email protected]>
On Thursday 02 March 2006 10:59, Jens Axboe wrote:
[dropping closed suse list. Please never put both closed and open lists into the same cc list]
Quoted 6 lines
libata should also handle this case better. Usually we just need to defer command handling if the
dma_map_sg()fails. Changingata_qc_issue()to return nsegments for success, 0 for defer failure, and -1 for permanent failure should be enough. The SCSI path is easy at least, as we can just ask for a defer there. The internalqc_issueis a little more tricky.
Yes I've been thinking about adding a new sleeping interface to the IOMMU that would block for new space to handle this. If I did that - would libata be able to use it?
-Andi