All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: "David S. Miller" <davem@redhat.com>
Cc: linux-mtd@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: jmorris@intercode.com.au
Cc: Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH RFC] 1/2 central workspace for zlib
Date: 31 May 2003 11:09:19 +0200	[thread overview]
Message-ID: <1054372158.5259.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030531075615.GA25089@wohnheim.fh-wedel.de>

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

On Sat, 2003-05-31 at 09:56, Jörn Engel wrote:
> CC List pruned a little.
> 
> On Fri, 30 May 2003 23:55:05 -0700, David S. Miller wrote:
> >    From: Jörn Engel <joern@wohnheim.fh-wedel.de>
> >    
> >    How about preemption?  zlib operations take their time, so at least on
> >    up, it makes sense to preempt them, when not in softirq context.  Can
> >    this still be done lockless?
> > 
> > You'll need to disable preemption.
> 
> My gut feeling claims that this would hurt interactivity. 

the code is decompressing data that was 4096 bytes originally. I doubt
that will be anything close to some real wallclock time nowadays....

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Arjan van de Ven <arjanv@redhat.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: "David S. Miller" <davem@redhat.com>,
	jmorris@intercode.com.au, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH RFC] 1/2 central workspace for zlib
Date: 31 May 2003 11:09:19 +0200	[thread overview]
Message-ID: <1054372158.5259.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030531075615.GA25089@wohnheim.fh-wedel.de>

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

On Sat, 2003-05-31 at 09:56, Jörn Engel wrote:
> CC List pruned a little.
> 
> On Fri, 30 May 2003 23:55:05 -0700, David S. Miller wrote:
> >    From: Jörn Engel <joern@wohnheim.fh-wedel.de>
> >    
> >    How about preemption?  zlib operations take their time, so at least on
> >    up, it makes sense to preempt them, when not in softirq context.  Can
> >    this still be done lockless?
> > 
> > You'll need to disable preemption.
> 
> My gut feeling claims that this would hurt interactivity. 

the code is decompressing data that was 4096 bytes originally. I doubt
that will be anything close to some real wallclock time nowadays....

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-05-31  9:09 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 14:49 [PATCH RFC] 1/2 central workspace for zlib Jörn Engel
2003-05-30 14:49 ` Jörn Engel
2003-05-30 15:29 ` James Morris
2003-05-30 15:29   ` James Morris
2003-05-30 17:43   ` Jörn Engel
2003-05-30 17:43     ` Jörn Engel
2003-05-31  0:14     ` David S. Miller
2003-05-31  0:14       ` David S. Miller
2003-05-31  6:48       ` Jörn Engel
2003-05-31  6:48         ` Jörn Engel
2003-05-31  6:55         ` David S. Miller
2003-05-31  6:55           ` David S. Miller
2003-05-31  7:56           ` Jörn Engel
2003-05-31  7:56             ` Jörn Engel
2003-05-31  7:59             ` David S. Miller
2003-05-31  7:59               ` David S. Miller
2003-05-31  8:11               ` Jörn Engel
2003-05-31  8:11                 ` Jörn Engel
2003-05-31  8:12                 ` David S. Miller
2003-05-31  8:12                   ` David S. Miller
2003-05-31  8:22             ` Con Kolivas
2003-05-31  8:22               ` Con Kolivas
2003-06-01  1:25               ` Matt Mackall
2003-06-01  1:25                 ` Matt Mackall
2003-06-02 12:19                 ` Jörn Engel
2003-06-02 12:19                   ` Jörn Engel
2003-05-31  9:09             ` Arjan van de Ven [this message]
2003-05-31  9:09               ` Arjan van de Ven
2003-05-31  6:20   ` David S. Miller
2003-05-31  6:20     ` David S. Miller
2003-05-31 10:51     ` James Morris
2003-05-31 10:51       ` James Morris
2003-05-31 11:07       ` Jörn Engel
2003-05-31 11:07         ` Jörn Engel
2003-05-31 15:44 ` Joakim Tjernlund
2003-06-02 12:26   ` Jörn Engel
2003-06-02 13:03     ` Joakim Tjernlund
2003-06-02 13:32       ` Jörn Engel
2003-06-02 15:15 ` matsunaga
2003-06-02 15:15   ` matsunaga
2003-06-02 15:36   ` Jörn Engel
2003-06-02 15:36     ` Jörn Engel
2003-06-02 15:40     ` David Woodhouse
2003-06-02 15:40       ` David Woodhouse
2003-06-02 15:53       ` Jörn Engel
2003-06-02 15:53         ` Jörn Engel
2003-06-02 15:59         ` David Woodhouse
2003-06-02 15:59           ` David Woodhouse
2003-06-02 16:37           ` Jörn Engel
2003-06-02 16:37             ` Jörn Engel
2003-06-02 19:36             ` David Woodhouse
2003-06-02 19:36               ` David Woodhouse
2003-06-02 20:54               ` Jörn Engel
2003-06-02 20:54                 ` Jörn Engel
2003-06-02 16:07     ` matsunaga
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=1054372158.5259.0.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=davem@redhat.com \
    --cc=joern@wohnheim.fh-wedel.de \
    /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.