[lkml]   [2007]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G
    William Lee Irwin III wrote:
    > William Lee Irwin III wrote:
    >>> !CONFIG_X86_PAE && CONFIG_HIGHMEM64G doesn't make sense and is not allowed
    >>> by this patch. CONFIG_X86_PAE && !CONFIG_HIGHMEM64G works here.
    > On Thu, Jun 07, 2007 at 08:38:22PM -0700, H. Peter Anvin wrote:
    >> But what's the point?
    >> If you're going to divorce these, at least do it in a way that makes
    >> sense, specifically the two independent variables are PAE and HIGHMEM.
    >> PAE and !HIGHMEM does make (some amount of) sense, due to no kmap overhead.
    > Beg your pardon? Are you reading the patch description correctly?

    I mean, with your patch CONFIG_HIGHMEM4G versus CONFIG_HIGHMEM64G really
    don't make sense as separate selections anymore.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-06-08 05:47    [W:0.019 / U:69.184 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site