All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org,
	marcelo@conectiva.com.br, davem@redhat.com
Subject: Re: [Linux-ia64] patch to no longer use ia64's software mmu
Date: 04 Dec 2001 15:25:15 +0100	[thread overview]
Message-ID: <je4rn7njuc.fsf@sykes.suse.de> (raw)
In-Reply-To: <20011203160059.A2022@devserv.devel.redhat.com>
In-Reply-To: <20011203160059.A2022@devserv.devel.redhat.com> (Arjan van de Ven's message of "Mon, 3 Dec 2001 16:00:59 -0500")

Arjan van de Ven <arjanv@redhat.com> writes:

|> Hi,
|> 
|> The patch below (against 2.4.16) makes the ia64 port no longer use the (VERY
|> slow) software IO mmu but makes it use the same mechanism the x86 PAE port
|> uses: it lets the higher layers take care of the proper bouncing of
|> PCI-unreachable memory. The implemenation is pretty simple; instead of
|> having a 4Gb GFP_DMA zone and a <rest of ram> GFP_KERNEL zone, the ia64 port
|> now has a 4Gb GFP_DMA zone and a <rest of ram> GFP_HIGH zone.
|> Since the ia64 cpu can address all of this memory directly, the kmap() and
|> related functions are basically nops. 

I tried it, but it doesn't compile: kmap_prot and kmap_pte are undefined.
If they are not used on ia64, then the reference in kernel/ksyms.c must be
removed.

Andreas.

-- 
Andreas Schwab                                  "And now for something
Andreas.Schwab@suse.de				completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5

  parent reply	other threads:[~2001-12-04 14:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 21:00 patch to no longer use ia64's software mmu 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-03 21:00 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

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=je4rn7njuc.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=arjanv@redhat.com \
    --cc=davem@redhat.com \
    --cc=linux-ia64@linuxia64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.