lkml.org 
[lkml]   [2004]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Problem with ioremap which returns NULL in 2.6 kernel
    Hello,

    Zwane Mwaikambo wrote:
    >>>probably too large an area to be remapping. Try remapping only the
    >>>memory area needed, and not the entire area.
    >>Is there a way, to increase the size, which could be remapped, or is
    >>there a way, to find out what is the maximum size which could be remapped?
    >>Thank you very much for the fast answer!
    > You could try a 4G/4G enabled kernel, /proc/meminfo tells you how much
    > vmalloc (ioremap) space there is too.

    VmallocTotal: 245752 kB
    VmallocUsed: 137720 kB
    VmallocChunk: 107904 kB

    Okay, i see the problem now, the largest piece of memory which could be
    allocated is 107904 kB, right?

    Is the 4G/4G split already in the kernel? If yes, which entry activates it?

    BTW, CONFIG_HIGHMEM4G is enabled already :-)

    Thanks for the hint!


    Best regards,


    Markus Lidel
    ------------------------------------------
    Markus Lidel (Senior IT Consultant)

    Shadow Connect GmbH
    Carl-Reisch-Weg 12
    D-86381 Krumbach
    Germany

    Phone: +49 82 82/99 51-0
    Fax: +49 82 82/99 51-11

    E-Mail: Markus.Lidel@shadowconnect.com
    URL: http://www.shadowconnect.com
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:03    [W:0.030 / U:89.756 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site