Is there any benefit/point to enabling HIGHMEM when using this patch, assuming that physical memory is smaller than the address space? For example, when using VMSPLIT_3G_OPT on a box with 1G of memory. Thanx! - 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/
- Follow-Ups:
- Re: [PATCH ] VMSPLIT config options (with default config fixed)
- From: Mark Lord <lkml@rtr.ca>
- Re: [PATCH ] VMSPLIT config options (with default config fixed)
- References:
- Re: 2G memory split
- From: Ingo Molnar <mingo@elte.hu>
- Re: 2G memory split
- From: Jens Axboe <axboe@suse.de>
- Re: 2G memory split
- From: Byron Stanoszek <gandalf@winds.org>
- Re: 2G memory split
- From: Jens Axboe <axboe@suse.de>
- Re: 2G memory split
- From: Linus Torvalds <torvalds@osdl.org>
- Re: 2G memory split
- From: Mark Lord <lkml@rtr.ca>
- Re: 2G memory split
- From: Jens Axboe <axboe@suse.de>
- Re: 2G memory split
- From: Mark Lord <lkml@rtr.ca>
- Re: 2G memory split
- From: Mark Lord <mlord@pobox.com>
- [PATCH ] VMSPLIT config options (with default config fixed)
- From: Mark Lord <lkml@rtr.ca>
- Re: 2G memory split
- Prev by Date: [PATCH] acpi: remove function tracing macros
- Next by Date: Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
- Previous by thread: Re: [PATCH ] VMSPLIT config options (with default config fixed)
- Next by thread: Re: [PATCH ] VMSPLIT config options (with default config fixed)
- Index(es):
 |