Re: Problem with ioremap which returns NULL in 2.6 kernel

[Markus Lidel <Markus.Lidel@shadowconnect.com>]

[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]

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?
 >
> No it's not in the current kernel, you'd have to download the patch, the
> most uptodate being the one in the Fedora/Redhat kernel tree.

Okay, thank you very much!

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

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3512 bytes --]