public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@suse.de>
Cc: Jens Axboe <axboe@suse.de>, Michael Monnerie <m.monnerie@zmi.at>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
Date: Thu, 02 Mar 2006 07:33:35 -0500	[thread overview]
Message-ID: <4406E61F.80306@pobox.com> (raw)
In-Reply-To: <200603021326.33220.ak@suse.de>

Andi Kleen wrote:
> On Thursday 02 March 2006 13:16, Jeff Garzik wrote:
> 
> 
>>>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?
>>
>>No :(  We map inside a spin_lock_irqsave.
> 
> 
> Would it be easily possible to change that or is it difficult?
> 
> Also with the blocking interface there might be possible deadlock issues 
> because it will be essentially similar to allocating memory during IO.
> But I think it's probably safe.

The SCSI layer submits stuff to libata inside spin_lock_irqsave(), and 
from there we DMA-map and send straight to hardware.

So, changing the hot path to permit sleeping would be difficult and add 
needless complexity, IMO.

I would rather pay the penalty of resubmitting if the 
map-inside-spinlock fails, than to slow down the hot path.

	Jeff




  parent reply	other threads:[~2006-03-02 12:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 23:23 PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution Michael Monnerie
2006-03-02  1:03 ` Andi Kleen
2006-03-02  9:59   ` Jens Axboe
2006-03-03  8:16   ` Chris Wedgwood
2006-03-03 11:00     ` Andi Kleen
     [not found] ` <200603021316.38077.ak@suse.de>
     [not found]   ` <4406E226.4050806@pobox.com>
2006-03-02 12:26     ` Andi Kleen
2006-03-02 12:31       ` Jens Axboe
2006-03-02 12:33       ` Jeff Garzik [this message]
     [not found]   ` <20060302123033.GL4329@suse.de>
2006-03-02 13:09     ` Andi Kleen
2006-03-02 13:10       ` Jens Axboe
2006-03-02 13:33         ` Andi Kleen
2006-03-02 13:33           ` Jens Axboe
2006-03-02 13:46             ` Andi Kleen
2006-03-02 13:49               ` Jens Axboe
2006-03-02 13:58                 ` Andi Kleen
2006-03-02 14:14                   ` Jens Axboe
2006-03-02 14:35                     ` Andi Kleen
2006-03-02 14:38                       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2006-03-03 21:27 Allen Martin
2006-03-03 22:12 ` Andi Kleen
2006-03-03 22:23   ` Jeff Garzik
2006-03-03 22:32     ` Andi Kleen
2006-03-04  6:34     ` Michael Monnerie
     [not found] <5Mq18-1Na-21@gated-at.bofh.it>
     [not found] ` <5MqNc-2Y5-3@gated-at.bofh.it>
     [not found]   ` <5MqX4-39H-21@gated-at.bofh.it>
     [not found]     ` <5MyAS-5zh-5@gated-at.bofh.it>
2006-03-07  0:15       ` Robert Hancock
2006-04-02  7:51         ` Joerg Bashir
2006-04-02  8:00           ` Muli Ben-Yehuda
2006-04-02  8:24             ` Joerg Bashir
2006-04-02 11:16           ` Andi Kleen

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=4406E61F.80306@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ak@suse.de \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.monnerie@zmi.at \
    /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