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: Mon, 03 Dec 2001 21:47:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805588@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805585@msgid-missing>
Arjan> Hi, The patch below (against 2.4.16) makes the ia64 port no
Arjan> longer use the (VERY slow) software IO mmu but makes it use
Arjan> the same mechanism the x86 PAE port uses: it lets the higher
Arjan> layers take care of the proper bouncing of PCI-unreachable
Arjan> memory. The implemenation is pretty simple; instead of having
Arjan> a 4Gb GFP_DMA zone and a <rest of ram> GFP_KERNEL zone, the
Arjan> ia64 port now has a 4Gb GFP_DMA zone and a <rest of ram>
Arjan> GFP_HIGH zone. Since the ia64 cpu can address all of this
Arjan> memory directly, the kmap() and related functions are
Arjan> basically nops.
Arjan> The result: 100 mbit ethernet performance on a ia64 machine
Arjan> with 32Gb of ram increased more than 4x (from 20 mbit to 95
Arjan> mbit)....
Arjan> The only downside is that the current kernel will always
Arjan> bounce buffer disk IO even if the scsi card is 64 bit PCI
Arjan> capable; Jens Axboe's block highmem patch fixes that downside
Arjan> nicely though.
How soon will Jens' patch make it into the official tree? I think
that would be a pre-requisite before switching to a highmem based
implementation.
Another concern I have is that, fundamentally, I dislike the idea of
penalizing all IA-64 platforms due to one chipset that is, shall we
say, "lacking" (i.e., doesn't have an I/O TLB).
Could someone comment on whether the 870 will have I/O TLB support
(private mail is fine, if you don't feel comfortable sending mail to
all the lists...).
Thanks,
--david
next prev parent reply other threads:[~2001-12-03 21:47 UTC|newest]
Thread overview: 24+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 21:00 Arjan van de Ven
2001-12-03 21:47 ` [Linux-ia64] " David Mosberger
2001-12-03 21:53 ` Arjan van de Ven
2001-12-04 9:36 ` Alan Cox
2001-12-04 16:26 ` David Mosberger
2001-12-04 16:32 ` Arjan van de Ven
2001-12-04 17:18 ` Alan Cox
2001-12-04 17:43 ` David Mosberger
2001-12-04 17:59 ` Alan Cox
2001-12-04 18:06 ` David Mosberger
2001-12-04 18:19 ` Alan Cox
2001-12-04 18:14 ` David Mosberger
2001-12-04 20:22 ` David S. Miller
2001-12-04 20:32 ` David Mosberger
2001-12-04 14:25 ` Andreas Schwab
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-105590698805588@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.