It seems that the kmalloc() function on 2.4.18 provides memory
allocation blocks on 8-byte boundaries. 2.5.52 provides memory
allocation blocks on 4-byte boundaries.
We have run into an issue with a device driver developed for 2.4.18 and
ported to 2.5.52. The driver requires buffers that are allocated on
Can anyone explain why this difference in buffer boundaries exists?
Any suggestions to ensure that the buffer allocation is 8-byte bounded?
Can we write a my_kmalloc() function that would always return an 8-byte
Thanks in advance,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 07 2003 - 22:00:17 EST