mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam Khan" <adam.khan@cavium.com>
To: <linux-kernel@vger.kernel.org>
Cc: "'Adam Khan'" <adam.khan@cavium.com>, <kodol2000@hanmir.com>
Subject: Memory allocation differences between 2.4.18 and 2.5.52
Date: Wed, 2 Apr 2003 11:21:47 -0800	[thread overview]
Message-ID: <000b01c2f94d$1be53780$7710a8c0@D6XKZR11> (raw)


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 
 




                 reply	other threads:[~2003-04-02 19:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000b01c2f94d$1be53780$7710a8c0@D6XKZR11' \
    --to=adam.khan@cavium.com \
    --cc=kodol2000@hanmir.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®