From: Bob Doyle <doyle@primenet.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: BusLogic cleanup
Date: Wed, 07 Jan 2004 22:12:56 -0700 [thread overview]
Message-ID: <3FFCE6D8.9E57769B@primenet.com> (raw)
In-Reply-To: 20040107153149.A29756@infradead.org
Christoph Hellwig wrote:
>
> On Thu, Jan 01, 2004 at 11:47:26PM -0700, Bob Doyle wrote:
> > I'm starting to do some cleanup to the BusLogic SCSI driver.
> > Since I'm a rank-newbie at anything SCSI, I thought I'd post a snap-shot
> > of where I am, and solicity direction and comments from the experts...
> >
> > Please review and comment.
>
> Patch looks okay so far.
Good. I don't feel like a dummy now...
> > - I'd really really like to run the code through 'indent' to match the
> > kernel coding standards but for now I don't want to confuse formatting
> > changes with code changes. It is very difficult to read as it is
> > currently formatted.
>
> Indeed. But it's not only a problem of indentation, but also of horrible
> naming of datatypes, structure members & variable names. You'll have to
> to some major work on these first otherwise a driver that is run through
> Lindent might be even more unreadable due to gazillions of linebreaks.
I know. I ran it though lindent and it was unreadable in less than 200
columns. I want to get the EH fixed and accepted then I start submitting
the 'beautification' changes. Those changes affect virtually every line
of code. I'll choke it down for now.
> A good start would be to kill the silly typedefs for kernel / scsi datatypes..
Already done in my tree. I was afraid that it would not be accepted.
For now, removing the typedefs just makes the linebreak issue worse.
> > So - now the questions...
> >
> > How do I test the eh_* handler functions? I've tried everything
> > I can think of to provoke them but haven't managed to. For now,
> > I don't know if they work or not.
>
> The best testcase would be a faulty disk. You could also try to get
> into EH szenarios by wrong termination / cabling - but who wants to do
> that to his system?
I saw that there was a scsi ramdisk driver to check the midlayer EH.
I was just wondering if there was some magic sysfs mechanism (or something)
excercise the driver EH. Anyway I have a junk disk that I might
be able to wound.
> > Also I clearly don't understand the command completion in the
> > context the error handlers. Do the eh_* functions need to
> > do command completion?
>
> They shouldn't in theory, but for that you need to make sure the
> driver leaves all queuing to the midlayer. If you queue command
> internaally to the driver the midlayer obviously doesn't know
> about them. One more reason not to do that.
Hmm. I haven't spent much time reading the midlayer code. I didn't know
that midlayer did command queuing. Are you recommending that the
driver-level queuing be removed?
Are the BusLogic docs anywhere anymore? The mylex page re-directs
to LSI Logic.
Sorry for all the questions...
Regards,
Bob.
next prev parent reply other threads:[~2004-01-08 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 6:47 BusLogic cleanup Bob Doyle
2004-01-07 15:31 ` Christoph Hellwig
2004-01-07 17:02 ` Chiaki
2004-01-08 5:12 ` Bob Doyle [this message]
2004-01-08 15:26 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:58 Cress, Andrew R
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=3FFCE6D8.9E57769B@primenet.com \
--to=doyle@primenet.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
/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.