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] patch to no longer use ia64's software mmu
Date: Tue, 04 Dec 2001 20:32:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805609@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805585@msgid-missing>

>>>>> On Tue, 04 Dec 2001 12:22:54 -0800 (PST), "David S. Miller" <davem@redhat.com> said:

  DaveM> If what you are asking is should we tweak the APIs again so
  DaveM> that situations like current IA64 can be done more sanely in
  DaveM> the PCI DMA layer, I say definitely no.

I certainly agree that the PCI DMA interface shouldn't be tweaked just
because of IA64.  What I'm wondering is whether we'll have to tweak it
anyhow to more gracefully handle the case where a hardware I/O TLB
runs out of space.  If so, I think the software I/O TLB makes sense.

  DaveM> There really is no excuse for the current IA64 hardware
  DaveM> situation, there were probably well over 3 or 4 major 64-bit
  DaveM> platforms from competitors, whose PCI controllers were pretty
  DaveM> well documented publicly, from which Intel could have derived
  DaveM> a working 64-bit platform PCI controller design.

Well, I won't comment on *this* one! ;-))

	--david


      parent reply	other threads:[~2001-12-04 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 21:00 [Linux-ia64] patch to no longer use ia64's software mmu Arjan van de Ven
2001-12-03 21:47 ` David Mosberger
2001-12-03 21:53 ` Arjan van de Ven
2001-12-04 18:14 ` David Mosberger
2001-12-04 18:19 ` Alan Cox
2001-12-04 19:55 ` David Mosberger
2001-12-04 19:56 ` David Mosberger
2001-12-04 19:56 ` David Mosberger
2001-12-04 20:22 ` David S. Miller
2001-12-04 20:32 ` David Mosberger [this message]

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-105590698805609@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