mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@suse.cz>
To: Adrian Bunk <bunk@stusta.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: ALSA: Is CONFIG_SND_DEBUG_MEMORY really required?
Date: Tue, 21 Jun 2005 16:49:43 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0506211643080.18102@pnote.perex-int.cz> (raw)
In-Reply-To: <20050621144041.GP3666@stusta.de>

On Tue, 21 Jun 2005, Adrian Bunk wrote:

> Hi,
> 
> I was a bit surprised to discover that ALSA has it's own memory 
> debugging infrastructure.
> 
> Is there a reason why CONFIG_DEBUG_SLAB isn't good enough for ALSA?

We're ready to move to something other, but standard allocation 
routines should be extended to handle "allocation pools".

We're able to detect quickly memory leaks in our code.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

      reply	other threads:[~2005-06-21 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 14:40 Adrian Bunk
2005-06-21 14:49 ` Jaroslav Kysela [this message]

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=Pine.LNX.4.58.0506211643080.18102@pnote.perex-int.cz \
    --to=perex@suse.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=bunk@stusta.de \
    --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®