From: David Howells <dhowells@redhat.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: dhowells@redhat.com, Russell King <rmk@arm.linux.org.uk>,
akpm@linux-foundation.org, mm-commits@vger.kernel.org,
hpa@zytor.com, ink@jurassic.park.msu.ru, kkojima@rr.iij4u.or.jp,
lethal@linux-sh.org, mingo@elte.hu, mpm@selenic.com,
rc@rc0.org.uk, rth@twiddle.net, starvik@axis.com,
takata@linux-m32r.org, tglx@linutronix.de,
ysato@users.sourceforge.jp,
Byron Bradley <byron.bbradley@gmail.com>,
linux-kernel@vger.kernel.org, michael@free-electrons.com
Subject: Re: + inflate-refactor-inflate-malloc-code.patch added to -mm tree
Date: Wed, 12 Mar 2008 14:47:31 +0000 [thread overview]
Message-ID: <13565.1205333251@redhat.com> (raw)
In-Reply-To: <20080218140704.4e0d6dba@crazy>
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> inflate: refactor inflate malloc code
>
> Inflate requires some dynamic memory allocation very early in the boot
> process and this is provided with a set of four functions:
> malloc/free/gzip_mark/gzip_release.
>
> The old inflate code used a mark/release strategy rather than
> implement free. This new version instead keeps a count on the number
> of outstanding allocations and when it hits zero, it resets the malloc
> arena.
>
> This allows removing all the mark and release implementations and
> unifying all the malloc/free implementations.
>
> The architecture-dependent code must define two addresses:
> - free_mem_ptr, the address of the beginning of the area in which
> allocations should be made
> - free_mem_end_ptr, the address of the end of the area in which
> allocations should be made. If set to 0, then no check is made on
> the number of allocations, it just grows as much as needed
>
> The architecture-dependent code can also provide an arch_decomp_wdog()
> function call. This function will be called several times during the
> decompression process, and allow to notify the watchdog that the
> system is still running. If an architecture provides such a call, then
> it must define ARCH_HAS_DECOMP_WDOG so that the generic inflate code
> calls arch_decomp_wdog().
>
> Work initially done by Matt Mackall <mpm@selenic.com>, updated to a
> recent version of the kernel by me.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Works on MN10300.
Acked-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2008-03-12 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 20:10 + inflate-refactor-inflate-malloc-code.patch added to -mm tree akpm
[not found] ` <20080215203103.GA22118@flint.arm.linux.org.uk>
2008-02-18 13:07 ` Thomas Petazzoni
2008-03-12 13:49 ` Thomas Petazzoni
2008-03-12 14:47 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 3:29 akpm
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=13565.1205333251@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=byron.bbradley@gmail.com \
--cc=hpa@zytor.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@free-electrons.com \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rc@rc0.org.uk \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@free-electrons.com \
--cc=ysato@users.sourceforge.jp \
/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.