Re: HIGH MEMORY access

From: Manfred Spraul (manfreds@colorfullife.com)
Date: Fri Mar 03 2000 - 12:44:42 EST

Next message: Stephen C. Tweedie: "Re: Changes in the sockets: SIGIO handling"
Previous message: Rik van Riel: "Re: Linux 2.2.15pre12"
In reply to: nathan.zook@amd.com: "RE: HIGH MEMORY access"
Next in thread: david parsons: "Re: HIGH MEMORY access"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

nathan.zook@amd.com wrote:
>
> This is changing. The new patches will be reclaim-enabled, so those pages
> will be mapped, and the max_pfn-class variables will reflect their presence.
>
and what if someone boots with "mem=32M", or if the bios supplies a
bogus pointer? or if the bios returns a pointer to a rom chip at 4 GB?
IMHO kmap() is intended for memory that's returned from
gfp(|GFP_HIHMEM), but not for external pointers.

-- Manfred

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/

Next message: Stephen C. Tweedie: "Re: Changes in the sockets: SIGIO handling"
Previous message: Rik van Riel: "Re: Linux 2.2.15pre12"
In reply to: nathan.zook@amd.com: "RE: HIGH MEMORY access"
Next in thread: david parsons: "Re: HIGH MEMORY access"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Mar 07 2000 - 21:00:15 EST