mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: dalecki@evision-ventures.com (Martin Dalecki)
Cc: axboe@suse.de (Jens Axboe),
	zwane@linux.realnet.co.sz (Zwane Mwaikambo),
	linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: [PATCH] 2.5.6-pre2 IDE cleanup 16
Date: Wed, 6 Mar 2002 00:33:55 +0000 (GMT)	[thread overview]
Message-ID: <E16iPNT-0004tb-00@the-village.bc.nu> (raw)
In-Reply-To: <3C84B1FB.2050003@evision-ventures.com> from "Martin Dalecki" at Mar 05, 2002 12:54:35 PM

> No quite my plan is:
> 
> 1. Rip it off.
> 2. Reimplement stuff if and only if someone really shows pressure
> for using it.
> 
> The "command parsing" excess is certainly going to go.

Its maybe handy actually. Without command parsing I can tell the drive to
do anything without good control - you know say like all the upcoming SSSCA
encrypt chunks of your harddisk so you can never get them back stuff.

The important bit is that for each command you must know the sequence of
phases. Get it wrong and your storage system goes off to visit undefined
states. I don't like my disks in undefined states because it tends to leave
them with undefined content.

Two things I do think wants considering

#1	Can the same thing be done by passing the command and sequence of
	transitions from user space (scsi generic takes that approach but
	scsi is a little more forgiving since the bogus transition will
	screw your command in a "oh whoops" detectable manner). IDE
	has a nice habit of explaining you screwed up by scribbling on
	the disk and/or locking solid

#2	Shoot all the little routines and make them into a table.

That would tidy it no end. 


  parent reply	other threads:[~2002-03-06  0:19 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  7:54 [PATCH] per-cpu areas Rusty Russell
2002-03-05 10:51 ` [PATCH] 2.5.6-pre2 IDE cleanup 16 Martin Dalecki
2002-03-05 11:07   ` Zwane Mwaikambo
2002-03-05 11:28     ` Jens Axboe
2002-03-05 11:54       ` Martin Dalecki
2002-03-05 12:04         ` Jens Axboe
2002-03-05 12:09           ` Martin Dalecki
2002-03-06  0:33         ` Alan Cox [this message]
2002-03-06  9:51           ` Martin Dalecki
2002-03-05 11:48     ` Martin Dalecki
2002-03-06  0:34       ` Alan Cox
2002-03-05 12:36     ` Anton Altaparmakov
2002-03-05 12:36       ` Martin Dalecki
2002-03-05 12:35         ` Zwane Mwaikambo
2002-03-06  0:28         ` Alan Cox
2002-03-05 12:47       ` Anton Altaparmakov
2002-03-05 12:52         ` Martin Dalecki
2002-03-06  1:40           ` Alan Cox
2002-03-06  8:56             ` Zwane Mwaikambo
2002-03-06  9:43             ` Martin Dalecki
2002-03-06  0:27       ` Alan Cox
2002-03-06 10:15         ` Martin Dalecki
2002-03-05 11:37   ` Arjan van de Ven
2002-03-05 11:51     ` Martin Dalecki
2002-03-05 21:19     ` Vojtech Pavlik
2002-03-05 21:42       ` Jeff Garzik
2002-03-05 21:46         ` Vojtech Pavlik
2002-03-06  9:19           ` Martin Dalecki
2002-03-06  1:08       ` Alan Cox
2002-03-06  9:45         ` Martin Dalecki
2002-03-06  0:41   ` Alan Cox
2002-03-06  9:15     ` benh
2002-03-06 11:07       ` Martin Dalecki
2002-03-06 11:12         ` Zwane Mwaikambo
2002-03-06 11:59           ` Martin Dalecki
2002-03-06 12:02         ` Meelis Roos
2002-03-06 12:11           ` Martin Dalecki
2002-03-06 16:01         ` Bill Davidsen
2002-03-06 20:36           ` Linus Torvalds
2002-03-06 17:00         ` benh
2002-03-06  9:49     ` Martin Dalecki
2002-03-06 13:46 Ronnie Sahlberg
2002-03-13 15:55 Rick A. Hohensee

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=E16iPNT-0004tb-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linux.realnet.co.sz \
    /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®