From: Arjan van de Ven <arjanv@redhat.com>
To: David Mosberger <davidm@hpl.hp.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
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: Mon, 3 Dec 2001 16:53:42 -0500 [thread overview]
Message-ID: <20011203165342.A16017@devserv.devel.redhat.com> (raw)
In-Reply-To: <20011203160059.A2022@devserv.devel.redhat.com> <15371.62205.231945.798891@napali.hpl.hp.com>
In-Reply-To: <15371.62205.231945.798891@napali.hpl.hp.com>; from davidm@hpl.hp.com on Mon, Dec 03, 2001 at 01:47:41PM -0800
On Mon, Dec 03, 2001 at 01:47:41PM -0800, David Mosberger wrote:
> 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.
I understood (and hope) "soon".
> 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).
I think some of it (if not all) can be abstracted in the machine vectors;
setting CONFIG_HIGHMEM doesn't hurt anything; the only important part is
where you put > 4Gb memory, eg in the NORMAL or HIGH zone. That choice,
while hardcoded in my patch, can obviously be made at runtime based on
capabilities of the machine... (the remaining overhead due to
kmap is (almost) zero already as the compiler will basically optimize
the inline away as it's a nop in the context of the users)
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2001-12-04 0:20 UTC|newest]
Thread overview: 15+ 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 [this message]
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=20011203165342.A16017@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox