All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Aman <aman@mistralsoftware.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Memory Leak
Date: Wed, 12 Mar 2003 13:29:39 -0700	[thread overview]
Message-ID: <20030312132939.C28769@home.com> (raw)
In-Reply-To: <001701c2e8d0$a017ef80$370da8c0@aman>; from aman@mistralsoftware.com on Thu, Mar 13, 2003 at 01:20:25AM +0530


On Thu, Mar 13, 2003 at 01:20:25AM +0530, Aman wrote:
>  Hi All
>  I am using consistent_alloc () to allocate consistent memory for DMA.  When
> I free the buffers using consistent_free(), the /proc/meminfo shows a
> memory leak of the buffer size allocated.
>
>  I have attached a  module code to allocate memory when inserted and free
>  when removed. The memory leak can be found using the command cat
> /proc/meminfo.

This was fixed three months ago in the development trees.

>  Also the consistent_alloc call gives an error something like "Kernel bug at
> cachemap.." if we try to allocate more than 2MB.

Of course, MAX_ORDER is 10 (in 2.4) and consistent_alloc() is based on
__get_free_pages().

I suggest reading "Understanding the Linux Kernel", "Linux Device
Drivers", and Documentation/* as a starting point for kernel
development.

If you simply must have more consistent memory then you can use
mem= on the command line to reduce the memory available to the
kernel and then use __ioremap/consistent_sync to map the massive
buffer and make it consistent.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-03-12 20:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 19:50 Memory Leak Aman
2003-03-12 20:29 ` Matt Porter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-19  5:14 [PATCH v26 2/2] status: add status.compareBranches config for multiple branch comparisons Jeff King
2026-01-20  9:49 ` Memory leak Harald Nordgren
2026-01-20 13:22   ` Harald Nordgren
2026-01-20 21:42     ` Junio C Hamano
2026-01-21 18:47       ` Junio C Hamano
2026-01-21 20:49         ` Jeff King
2026-01-22 15:03         ` Harald Nordgren
2026-01-22 18:19           ` Junio C Hamano
2008-04-09 13:54 hinko.kocevar
2003-03-09 16:46 matsunaga
2003-03-09 17:37 ` Charles Manning
2003-03-09 19:10 ` Thomas Gleixner
2003-03-09 23:10   ` matsunaga
2003-03-10 14:53     ` Thomas Gleixner
2003-03-10 14:14       ` David Woodhouse
2003-03-10 15:48         ` matsunaga
2003-03-10 16:02           ` David Woodhouse
2003-03-10 16:26             ` matsunaga
2003-03-10 17:04               ` David Woodhouse
2003-03-11 15:52                 ` matsunaga
2003-03-11 18:39                   ` Thomas Gleixner
2003-03-10 15:36       ` matsunaga
2003-03-11 17:50 ` David Woodhouse
2002-06-20 15:06 diekema_jon
2002-06-20  7:52 Skip Gaede
2002-06-22  2:22 ` Skip Gaede

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=20030312132939.C28769@home.com \
    --to=porter@cox.net \
    --cc=aman@mistralsoftware.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.