From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: art_k@o2.pl
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [Patch] 2.5.70-bk11 zlib reduce deflate workspace by 128k
Date: Fri, 6 Jun 2003 18:29:21 +0200 [thread overview]
Message-ID: <20030606162921.GA911@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030606170043.37965017.art_k@o2.pl>
On Fri, 6 June 2003 17:00:43 +0200, art_k@o2.pl wrote:
> Jörn Engel <joern@wohnheim.fh-wedel.de> (030606.160149,<20030606140149.GA20168@wohnheim.fh-wedel.de>):
> > Free lunch time. There are currently no users in the kernel that use
> > a memlevel >8, but we reserve space for 9. The patch saves 128k at no
> > cost.
>
> > /* Maximum value for memLevel in deflateInit2 */
> > #ifndef MAX_MEM_LEVEL
> > -# define MAX_MEM_LEVEL 9
> > +# define MAX_MEM_LEVEL 8
> > #endif
>
> i like the direction this is going, but when making these kind of changes
> it would be even better if the reasoning would be noted in a short comment
> (eg. "/* no users of memlevel>8 in kernel; saves 128k RAM */").
> That way the next person looking at that code would immediately know why
> that number was chosen.
Usually, you would be right. But in this case, the existing comments
in zconf.h match the situation *after* my patch. Looks good to me.
Jörn
--
But this is not to say that the main benefit of Linux and other GPL
software is lower-cost. Control is the main benefit--cost is secondary.
-- Bruce Perens
prev parent reply other threads:[~2003-06-06 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 14:01 Jörn Engel
[not found] ` <20030606170043.37965017.art_k@o2.pl>
2003-06-06 16:29 ` Jörn Engel [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=20030606162921.GA911@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=art_k@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®