* Memory allocation differences between 2.4.18 and 2.5.52
@ 2003-04-02 19:21 Adam Khan
0 siblings, 0 replies; only message in thread
From: Adam Khan @ 2003-04-02 19:21 UTC (permalink / raw)
To: linux-kernel; +Cc: 'Adam Khan', kodol2000
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
8-byte boundaries.
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
bounded buffer.
Thanks in advance,
Adam
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-04-02 19:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-02 19:21 Memory allocation differences between 2.4.18 and 2.5.52 Adam Khan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®