public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Richard Hirst <rhirst@linuxcare.com>
Subject: Re: [PATCH 2.5.59] sim710: cleanup/remove most cli()'s
Date: 04 Feb 2003 17:11:38 -0600	[thread overview]
Message-ID: <1044400300.3485.25.camel@mulgrave> (raw)
In-Reply-To: <200302041123.06204@bilbo.math.uni-mannheim.de>

On Tue, 2003-02-04 at 04:23, Rolf Eike Beer wrote:
> Hi,
> 
> the appended patch does the following:
> 
> -group all includes (except '#include "scsi_module.c"') together
> -add KERN_* to all printk's
> -add error checking for call of request_region
> -remove most cli() and use spin_lock instead
> -move help text to Documentation/scsi/sim710.txt
> -add a new debug target for debugging spinlocks
> -remove the magic numbers for request_region and release_region and use
>  SIM710_IOREGION_SIZE instead
> -same thing for the driver name
> -remove assignement to driver_template.proc_name which is already done before
>  in sim710.h
> 
> I have not broken this into peaces because for all changes (except the first
> of course) the corresponding lines are grouped together so it should be clear
> what I've done.
> 
> A kernel with this modification has booted yesterday and was tested under
> heavy loads succesfully.
> 
> What has to be done is:
> -remove the remaining two cli()
> -port this to the new driver model
> 
> I'm already working on this but it does not boot until now, so I'll delay this
> until it works.

Actually, since you're showing an interest in this driver, I think the
best thing to do would be to port it to use the 53c700 chip driver. 
Since the 53c700 already has all the sti/cli and DMA API issues sorted
out already, the only thing that would need to be done is to convert
sim710 to a template that speaks the new device model and initialises
the chip fields.

This would also bring synchronous operation and tag command queueing
virtually for free.

James



  parent reply	other threads:[~2003-02-04 23:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 10:23 [PATCH 2.5.59] sim710: cleanup/remove most cli()'s Rolf Eike Beer
2003-02-04 11:34 ` Christoph Hellwig
2003-02-04 23:11 ` James Bottomley [this message]
2003-02-05 15:03 ` Rolf Eike Beer
2003-02-06 16:35   ` James Bottomley
2003-02-07  7:26   ` Rolf Eike Beer
2003-02-08  3:57     ` James Bottomley
2003-02-11 10:55       ` Rolf Eike Beer
2003-02-11 18:30         ` James Bottomley

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=1044400300.3485.25.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rhirst@linuxcare.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