mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: James Morris <jmorris@intercode.com.au>
Cc: "David S. Miller" <davem@redhat.com>,
	dwmw2@infradead.org, matsunaga_kazuhisa@yahoo.co.jp,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] 1/2 central workspace for zlib
Date: Sat, 31 May 2003 13:07:43 +0200	[thread overview]
Message-ID: <20030531110743.GA24300@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Mutt.LNX.4.44.0305312025270.6696-100000@excalibur.intercode.com.au>

On Sat, 31 May 2003 20:51:04 +1000, James Morris wrote:
> On Fri, 30 May 2003, David S. Miller wrote:
> 
> > My understanding is that these are just scratchpads.  The contents
> > while a decompress/compress operation is not occuring does not
> > matter.
> 
> It depends on how the zlib library is used.  The filesystems and crypto
> code use it so that each operation is distinct, although it is possible to
> maintain compression history between operations: PPP does this via a
> sliding compression window, and there are other potential users such as
> ROHC.
> 
> One way of addressing this would to allow the user to supply their own 
> workspace if compression history needs to be maintained.

Agreed.  How much memory is needed for the history?  Most of the
workspace or substancially less?

> > So if we have 2 such scratchpads per cpu, one for normal and one for
> > BH context, his idea truly can work and be useful to everyone.
> > It would also be lockless on SMP.
> 
> And perhaps implement with a lazy allocation scheme so that these
> scratchpads are only allocated if needed (i.e. a caller does not provide
> its own workspace).

Disagreed.  Two scratchpads per cpu won't hurt in the mean case much
and lazy allocation wouldn't improve the worst case either.  Keep them
static and simple.

Jörn

-- 
With a PC, I always felt limited by the software available. On Unix, 
I am limited only by my knowledge.
-- Peter J. Schoenster

  reply	other threads:[~2003-05-31 10:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 14:49 Jörn Engel
2003-05-30 15:29 ` James Morris
2003-05-30 17:43   ` Jörn Engel
2003-05-31  0:14     ` David S. Miller
2003-05-31  6:48       ` Jörn Engel
2003-05-31  6:55         ` David S. Miller
2003-05-31  7:56           ` Jörn Engel
2003-05-31  7:59             ` David S. Miller
2003-05-31  8:11               ` Jörn Engel
2003-05-31  8:12                 ` David S. Miller
2003-05-31  8:22             ` Con Kolivas
2003-06-01  1:25               ` Matt Mackall
2003-06-02 12:19                 ` Jörn Engel
2003-05-31  9:09             ` Arjan van de Ven
2003-05-31  6:20   ` David S. Miller
2003-05-31 10:51     ` James Morris
2003-05-31 11:07       ` Jörn Engel [this message]
2003-06-02 15:15 ` matsunaga
2003-06-02 15:36   ` Jörn Engel
2003-06-02 15:40     ` David Woodhouse
2003-06-02 15:53       ` Jörn Engel
2003-06-02 15:59         ` David Woodhouse
2003-06-02 16:37           ` Jörn Engel
2003-06-02 19:36             ` David Woodhouse
2003-06-02 20:54               ` Jörn Engel
2003-06-02 16:07     ` matsunaga

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=20030531110743.GA24300@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=davem@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jmorris@intercode.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matsunaga_kazuhisa@yahoo.co.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 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®