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 19:56:33 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805606@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805585@msgid-missing>

>>>>> On Tue, 4 Dec 2001 17:18:17 +0000 (GMT), Alan Cox <alan@lxorguk.ukuu.org.uk> said:

  >> I think the issue at hand is whether, longer term, it is
  >> desirable to move all bounce buffer handling into the PCI DMA
  >> layer or whether Linux should continue to make bounce buffer
  >> management visible to drivers.  I'd be interested in hearing
  >> opinions.

  Alan> I think the performance figures we see currently answer that
  Alan> already.

The numbers I have seen so far don't make this obvious.  Tony Luck
reports 95Mbps with a CPU load of 20% after a fixing a performance bug
in the software I/O TLB.  Arjan reported the same 95Mbps figure with
the highmem approach.  Arjan didn't report the CPU load and neither
Tony nor Arjan specified the test environment they were using.

  Alan> IA64 also needs to correct its GFP_DMA to mean "low 16Mb" for
  Alan> ISA DMA. While there is no ISA DMA on ia64 (thankfully) many
  Alan> PCI cards have 26-31 bit limits.

We could do this if we there was a GFP_4GB zone.  Now that 2.5 is open
for business, it won't be long, right?

	--david


  parent reply	other threads:[~2001-12-04 19:56 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 [this message]
2001-12-04 19:56 ` David Mosberger
2001-12-04 20:22 ` David S. Miller
2001-12-04 20:32 ` David Mosberger

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