public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: PATCH: performance problems with swiotlb.c
Date: Mon, 03 Dec 2001 22:06:08 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805591@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805584@msgid-missing>

>>>>> On Mon, 3 Dec 2001 15:27:47 -0500, Arjan van de Ven <arjanv@redhat.com> said:

  Arjan> Unfortionatly the idea of a software MMU is broken by
  Arjan> design. The current DMA API does not allow for one in
  Arjan> practice, and, thankfully, there's also no need for one. The
  Arjan> linux kernel allows perfectly well for systems without IO MMU
  Arjan> and will do the right thing at higher layers, where things
  Arjan> CAN be done properly (for example, the software IOMMU cannot
  Arjan> sleep to wait for memory and hence panic()'s the kernel in
  Arjan> this case, while the higher layers often can either sleep (in
  Arjan> the case of the blockdevice layer) or just drop the packet on
  Arjan> near-OOM in the case of the network layer.

But longer term, the question is whether it is better to support
multiple bounce buffer schemes or whether the PCI DMA interface should
be enhanced to better handle "out of memory" situations.  In my
opinion, it would be better to enhance the PCI DMA interface with a
throttling/OOM-feedback mechanism.

Note that even with hardware I/O TLB, you can get into such
situations.  The only real difference is that the software I/O TLB
consumes memory primarily as a functiion of the amount of data being
buffered, whereas a hardware I/O TLB it's primarily limited by the
number of *descriptors* needed.

	--david


  reply	other threads:[~2001-12-03 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 20:27 [Linux-ia64] Re: PATCH: performance problems with swiotlb.c Arjan van de Ven
2001-12-03 22:06 ` David Mosberger [this message]
2001-12-03 22:10 ` Arjan van de Ven

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=marc-linux-ia64-105590698805591@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@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