From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: ioremap()/PCI sickness in 2.4.18-rc2 (FIXED ALMOST)
Date: Wed, 20 Feb 2002 15:20:11 -0700 [thread overview]
Message-ID: <20020220152011.A1252@vger.timpanogas.org> (raw)
In-Reply-To: <20020220103320.A32211@vger.timpanogas.org> <20020220103539.B32211@vger.timpanogas.org> <3C73DC34.E83CCD35@mandrakesoft.com> <20020220.093034.112623671.davem@redhat.com> <20020220110004.A32431@vger.timpanogas.org> <20020220145449.A1102@vger.timpanogas.org> <3C741A44.94FE4F56@mandrakesoft.com>
In-Reply-To: <3C741A44.94FE4F56@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Feb 20, 2002 at 04:51:00PM -0500
On Wed, Feb 20, 2002 at 04:51:00PM -0500, Jeff Garzik wrote:
> "Jeff V. Merkey" wrote:
> > regions of memory. I would propose that the maintainer of
> > vmalloc.c look at using 48 bit PTE entries or some other solution
> > as a way to alloc larger virtual address frames when the system has
> > a lot of physical memory. It's seems pretty lame to me for a machine
> > with 2 GB of physical memory not to have at lest 256 MB of address space
> > left over for address mapping.
>
> Instead of constantly trying to map >32-bit addresses onto 32-bit
> processors, why not just get a 64-bit processor?
>
> One constantly runs into limitations with highmem...
>
> Jeff
Sigh .... I am only using 2 GB on a 4GB capable processor (actually
a 64 GB capable processor). Looks like a patch is needed. Who is
maintaining vmalloc.c at present so I know who to submit a patch
to?
Jeff
>
>
>
> --
> Jeff Garzik | "Why is it that attractive girls like you
> Building 1024 | always seem to have a boyfriend?"
> MandrakeSoft | "Because I'm a nympho that owns a brewery?"
> | - BBC TV show "Coupling"
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-02-20 22:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 17:33 ioremap()/PCI sickness in 2.4.18-rc2 Jeff V. Merkey
2002-02-20 17:35 ` Jeff V. Merkey
2002-02-20 17:26 ` Jeff Garzik
2002-02-20 17:30 ` David S. Miller
2002-02-20 18:00 ` Jeff V. Merkey
2002-02-20 21:54 ` ioremap()/PCI sickness in 2.4.18-rc2 (FIXED ALMOST) Jeff V. Merkey
2002-02-20 21:51 ` Jeff Garzik
2002-02-20 22:20 ` Jeff V. Merkey [this message]
2002-02-20 22:53 ` Jeff V. Merkey
2002-02-20 23:06 ` Alan Cox
2002-02-20 23:35 ` Jeff V. Merkey
[not found] ` <mailman.1014247349.21244.linux-kernel2news@redhat.com>
2002-02-20 23:44 ` Pete Zaitcev
2002-02-20 22:10 ` Jeff V. Merkey
2002-02-20 22:08 ` arjan
2002-02-22 11:08 ` Steffen Persvold
2002-02-22 18:17 ` Jeff V. Merkey
2002-02-22 18:42 ` David Mosberger
2002-02-22 18:51 ` Jeff Garzik
2002-02-22 19:01 ` David Mosberger
2002-02-22 19:42 ` Jeff V. Merkey
2002-02-23 2:22 ` Richard Henderson
2002-02-20 18:44 ` ioremap()/PCI sickness in 2.4.18-rc2 Steffen Persvold
2002-02-20 20:36 ` Jeff V. Merkey
2002-02-22 11:49 ` Steffen Persvold
2002-02-22 18:21 ` Jeff V. Merkey
2002-02-20 17:46 ` Jeff V. Merkey
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=20020220152011.A1252@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jgarzik@mandrakesoft.com \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@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