linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>, Jonathan Corbet <corbet@lwn.net>,
	Boaz Harrosh <bharrosh@panasas.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Zach Brown <zach.brown@oracle.com>,
	Chris Mason <chris.mason@oracle.com>, Tejun Heo <tj@kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: LSF Papers online?
Date: Wed, 15 Apr 2009 15:38:20 +0200	[thread overview]
Message-ID: <200904151538.20546.bzolnier@gmail.com> (raw)
In-Reply-To: <20090415102829.7fec55f2@lxorguk.ukuu.org.uk>

On Wednesday 15 April 2009 11:28:29 Alan Cox wrote:
> > I just wanted to have clear vision of the process instead of "lets merge
> > it now and worry about real users later".
> 
> There was a simple vision which was to provide full coverage for all the
> relevant ATA controllers using the libata core ASAP and leave the old IDE
> code "as is". That was what was done.

You took the "shortcut" instead of fixing the issue the "proper" way.

Namely, you defined "relevant" and "full coverage" as you wanted.

Depending on the level of difficulty of the task.

Wasn't IDE PMAC relevant back in 2005?

It was much more relevant than CMD640 or legacy VLB drivers that you ported.

It is 2009 now and IDE PMAC is still much more relevant than some other
stuff that you're working on.

Wasn't 32-bit PIO important for embedded systems back then?
[it happened only recently]

You also threw in a bunch of regressions because you didn't start from
fixing IDE host drivers in incremental evolutionary way.

You didn't even care to backport some obvious/critical fixes to IDE,
the same IDE that all distributions (including _your_ past employer)
were still shipping.

Yes, doing it your way was faster for _you_ and gave _you_ huge competition
advantage but prevented any reasonable review/help from _other_ people.

Reinventing the whole subsystem is not a single person project.

It is just physically impossible to do it properly.

The complexity and the scale is too large and there will be always things
that you miss or that other people are better at.

> > Every uncomfortable technical issue raised was addressed with direct
> > "IDE is teh crap" shouting 
> 
> Sorry but you are re-inventing history here. The old IDE layer was crap,
> and for sound technical reasons including the error handling and the
> horrible locking problems from the design level up caused by the
> reset/error/timeout handling paths and the polled speed change on CRC
> error change down.

That was not the issue raised.

> I spent years working on that stuff. Throwing it all away was not my idea

So what?

This doesn't make you special in any way.

Few other people had similar experiences.

> of fun, but it was clearly the right technical decision. I'm very happy
> with the state of libata PATA.

Maybe it is the time to retire from kernel hacking then? ;)

You see, I'm not happy with the state of IDE, libata, SCSI, block
and many other things.  I know that I'll _never_ be.  I also bet that
most of people working with me feel in the exactly same way.

More seriously, it is 2009 now.

Four years after initial libata PATA introduction and I could still
spend few next weeks sending one IDE -> libata regression fix per day,
ranging from possible data corruption through lack of hardware support
to duplicated code [most of issues can be tracked back to 2005].

However I simply do not care.

I don't need libata PATA.

I don't use it, I'm not paid to work on it and it is not my project.

It seems that it I'm not the only one who misunderstood the free software.

If you are not interested in people wanting to improve _your_ project
then we can end up the discussion here.

You may not like me but this is pretty lame excuse for denying me
merit and in turn damaging _your_ own project.

Re-read my previous mail and ping me when you are back to the rational
thinking.

Till then I'm done with this topic.

  reply	other threads:[~2009-04-15 13:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49E335BA.3020103@panasas.com>
     [not found] ` <200904132340.21525.bzolnier@gmail.com>
     [not found]   ` <49E3BBB9.4040100@garzik.org>
     [not found]     ` <200904140324.59657.bzolnier@gmail.com>
2009-04-14 10:14       ` LSF Papers online? Jeff Garzik
2009-04-14 14:54         ` Bartlomiej Zolnierkiewicz
2009-04-14 15:40           ` Jeff Garzik
2009-04-14 16:54           ` Alan Cox
2009-04-14 22:09             ` Bartlomiej Zolnierkiewicz
2009-04-14 22:49               ` James Bottomley
2009-04-15  1:39                 ` Robert Hancock
2009-04-15  3:58                   ` James Bottomley
2009-04-15  8:30                     ` Alan Cox
2009-04-16  6:31                   ` Grant Grundler
2009-04-16 16:37                     ` James Bottomley
2009-04-16 17:45                       ` Matthew Wilcox
2009-04-14 23:14               ` Jeff Garzik
2009-04-15  9:28               ` Alan Cox
2009-04-15 13:38                 ` Bartlomiej Zolnierkiewicz [this message]
2009-04-15 14:56                   ` Alan Cox
2009-04-16 16:01                     ` Bartlomiej Zolnierkiewicz

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=200904151538.20546.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bharrosh@panasas.com \
    --cc=chris.mason@oracle.com \
    --cc=corbet@lwn.net \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=zach.brown@oracle.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;
as well as URLs for NNTP newsgroup(s).