Re: Re: About Internal Fragmentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2005-06-23 at 23:36, Mulyadi Santosa wrote:
> Dear Kuncoro....
...
> 
> > However, I had changed kmalloc to vmalloc, and resulted in system
> > panic. (page fault).
> > Do you have any idea why?
> 
> The only explanation I can think now: since vmalloc() allocate memory 
> that is only virtually contigous but not necessarily physically 
> contigous, it made several function related with hardware device 
> internal's work which always assume physically contigous memory fail to 
> work properly. Read the "Linux kernel Development" 1st edition page 175 
> about vmalloc(), there I got this raw conclusion
> 
  
  Before we run off making conclusions about what caused the panic, it
would be good to learn more about the problem: dmesg/oops output (if
available), source code that is calling vmalloc, etc.  It's always best
for me to assume that I did something stupid to cause an error (which is
99+% the case) than look for explanation in the kernel.

-- Bob

> regards
> 
> Mulyadi
> 
> 
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive:       http://mail.nl.linux.org/kernelnewbies/
> FAQ:           http://kernelnewbies.org/faq/
> 
> 


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux