![]() | |||||||||||
Messages in this thread |
Jes Sorensen schrieb: > Christian Hildner <christian.hildner@hob.de> writes: > > > David, > > > > you proposed me to use alloc_pages() instead of kmalloc() in order > > to get memory bigger than the 128K limit of the kmalloc() call. But > > even driver-developers don't want to handle with the page struct > > unless this is unavoidable. Which are the disadvantages of > > increasing the size limit of kmalloc() to 256K, 512K or 1M since > > machines are getting bigger and 64Bit machines break with current > > memory limitations? > > Because drivers needs to work on all architectures and relying on > different hahavior from kmalloc() is bad. > > Jes Jes, sorry for being unclear. I mean from increasing the kmalloc() size-limit all platforms would benefit. Christian PS: David, I am looking forward getting your book. You are doing a great job. - 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 13:23 [from the cache] ©2003-2008 | |||||||||||