From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Fwd: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
Date: Thu, 2 Mar 2006 13:25:03 +0100 [thread overview]
Message-ID: <200603021325.03560.ak@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 32 bytes --]
Sorry dropped l-k cc by mistake
[-- Attachment #2: Andi Kleen <ak@suse.de>: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution --]
[-- Type: text/plain, Size: 1295 bytes --]
From: Andi Kleen <ak@suse.de>
To: Jens Axboe <axboe@suse.de>
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 <m.monnerie@zmi.at>,
Jeff Garzik <jgarzik@pobox.com>
References: <200603020023.21916@zmi.at> <200603020203.49128.ak@suse.de> <20060302095959.GD4329@suse.de>
In-Reply-To: <20060302095959.GD4329@suse.de>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200603021316.38077.ak@suse.de>
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]
> libata should also handle this case better. Usually we just need to
> defer command handling if the dma_map_sg() fails. Changing
> ata_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 internal qc_issue is 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
reply other threads:[~2006-03-02 12:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200603021325.03560.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox