public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Corey Minyard <minyard@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Moving zlib so that others may use it
Date: Wed, 09 Jan 2002 22:08:57 -0800	[thread overview]
Message-ID: <3C3D2FF9.8040405@zytor.com> (raw)
In-Reply-To: <25006.1010627525@kao2.melbourne.sgi.com> <3C3D19AD.60306@acm.org>

Corey Minyard wrote:

> 
> I'm not sure I follow you here.  Do you want to completely separate the
> inflate and deflate stuff (so if something only needs one, it only has
> to include one)?  I'm not sure of the value, and it would be kind of a
> pain for maintenance (since zlib is from an external source).
> 
> As far as memory management, all the versions I am talking about are
> almost exactly the same, so that shouldn't be a problem.
> 


It is external, but it's quite well separated anyway.

Look at the inflate_fs one (fs/inflate_fs); it has both the memory 
management dealt with and decompression factored out...

	-hpa




  reply	other threads:[~2002-01-10  6:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 23:32 Moving zlib so that others may use it Corey Minyard
2002-01-09 23:36 ` H. Peter Anvin
2002-01-10  1:52 ` Keith Owens
2002-01-10  4:23   ` Corey Minyard
2002-01-10  4:44     ` Keith Owens
2002-01-10  5:13       ` Corey Minyard
2002-01-10  5:40         ` Keith Owens
2002-01-10 10:55           ` Thomas Capricelli
2002-01-10 14:40             ` Corey Minyard
2002-01-10 15:22             ` Corey Minyard
2002-01-10  9:37         ` Zygo Blaxell
2002-01-10 15:30           ` Tom Rini
2002-01-10 15:36       ` Tom Rini
2002-01-10 16:20         ` Corey Minyard
2002-01-10 16:35           ` Tom Rini
2002-01-10  4:33   ` Corey Minyard
2002-01-10  6:08     ` H. Peter Anvin [this message]
2002-01-10 14:13   ` David Woodhouse

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=3C3D2FF9.8040405@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.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