public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@openedhand.com>
To: Daniel Hazelton <dhazelton@enter.net>
Cc: akpm <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Hugh Dickins <hugh@veritas.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	David Woodhouse <dwmw2@infradead.org>,
	Nitin Gupta <nitingupta910@gmail.com>
Subject: Re: [PATCH -mm 0/5] LZO and swap write failure patches for -mm
Date: Mon, 04 Jun 2007 21:45:55 +0100	[thread overview]
Message-ID: <1180989955.6313.168.camel@localhost.localdomain> (raw)
In-Reply-To: <200706041337.51563.dhazelton@enter.net>

On Mon, 2007-06-04 at 13:37 -0400, Daniel Hazelton wrote:
> Yes - most of that work, IIRC, is related to the alignment issues that Herr 
> Oberhumer noted. As it stands, the alternative does work well for a large 
> number of the platforms that the kernel supports. With a little Kconfig magic 
> it could be made available *only* for those platforms that it currently 
> supports. Then people can help work on the alignment issues - possibly by 
> providing platform conditional code.

My patch was actually written with ARM machines in mind and has been
extremely well tested on it. A version which doesn't run on ARM is not
acceptable. Its also ironic that "platform conditional code" is what a
lot of that bloat you're so keen to remove is about.

> I'm not familiar with the zlib code, but it was included a long time ago - 
> since zlib was included I'm pretty certain that if it had been proposed today 
> it would have been NACK'd for the style violations and bloat.

Adrian's covered this. I also know how hard updating something like zlib
is (I was the last person to do it).

> You can take the time to produce a patch and spread FUD about the speed of a 
> competing patches code but you don't have the time to work on fixing a 
> cleaner implementation? I'll admit that actually working on fixing problems 
> in code can take more time, but still - the time taken for those pursuits 
> *could* have been spent actually working on fixing the problems.

I *have* spent some time on it.

My speed comments were actually pretty positive. Yes, I screwed up one
of the benchmarks (as have others proving its easily done) but I did
admit to it. My others were fair comment and some issues were addressed
as a result (but not all).

I'm going to stop here. I don't agree with the rest of your email and
you've a distorted view of whats been said.

Regards,

Richard


  parent reply	other threads:[~2007-06-04 20:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 15:36 [PATCH -mm 0/5] LZO and swap write failure patches for -mm Richard Purdie
2007-06-04 16:14 ` Daniel Hazelton
2007-06-04 16:52   ` Richard Purdie
2007-06-04 17:37     ` Daniel Hazelton
2007-06-04 18:34       ` Nitin Gupta
2007-06-04 20:45       ` Richard Purdie [this message]
2007-06-04 22:13         ` Daniel Hazelton
2007-06-04 18:26     ` Nitin Gupta
2007-06-04 20:06       ` Adrian Bunk
2007-06-05  5:30         ` Nitin Gupta
2007-06-05  5:50           ` Andrew Morton
2007-06-05  8:56             ` Richard Purdie
2007-06-04 20:58       ` Richard Purdie
2007-06-05  6:15         ` Christoph Hellwig

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=1180989955.6313.168.camel@localhost.localdomain \
    --to=rpurdie@openedhand.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhazelton@enter.net \
    --cc=dwmw2@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=nitingupta910@gmail.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