This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Glibc malloc & using madvise
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Richard Kralovic" <Richard dot Kralovic at inf dot ethz dot ch>
- Cc: libc-help at sourceware dot org
- Date: Tue, 28 Oct 2008 15:21:42 -0400
- Subject: Re: Glibc malloc & using madvise
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=VWrRuv4DJeyLIxlF8+oMtidNIOmyXMMT1wKkH/qH/cg=; b=hRDFQR0hvqvNN4oc624CuB4C17e/jcE5Lv9kS/qMoPqfC1NVVKA2Ovv1Jf66JbPz2g cbyXo3gx5G+b4lqwLavb+vKhEhs8nr6xemy6r2QKC1GLaD4HCz+Rq2Djx0jgoeLjzAQG qLqKz70dcTbrMYBI/b9gdu4dHOpFxw53fpuFw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=aql6VEx/BwIqUP0wnqSq8t8oLfdYU8DqFSIE81ptVZIzYQ1C/wI8ysyx8EPvZHuBnT HIv6jw41Ec/Tg132c+OT8qKyh7tX2r0oWBuxccdA3heFeVV47AfAORXWyJ47DRMLHF5d izuC6PtAzuFce+jy226BezR247I+8pJBNHRKI=
- References: <490763E9.1070701@inf.ethz.ch>
On Tue, Oct 28, 2008 at 3:11 PM, Richard Kralovic
<Richard.Kralovic@inf.ethz.ch> wrote:
> This patch did quite good job for me - memory usage of some applications
> (especially long-running ones with high peaks and deep valleys in memory
> usage, such as xserver and konqueror) dropped by tenths of megabytes, so
> there is more space for cache and less swapping in suspend/resume, and I
> have not noticed any slowdown. Is there any chance of applying this (or
> some similar) patch?
http://sources.redhat.com/glibc/wiki/Contribution%20checklist
- Please write a GNU ChangeLog
- Any test failures with your patch?
- What is your FSF xopyright assignment status?
Ultimately the chance of your patch going into glibc is almost zero.
You stand a better chance of getting your patch into Wolfram Gloger's
ptmalloc (*the* GLIBC malloc implementation), and then asking glibc to
import the change.
Cheers,
Calros.