From: Christoph Hellwig <hch@lst.de>
To: Adam Radford <aradford@amcc.com>
Cc: akpm@osdl.org, James.Bottomley@SteelEye.com, hch@lst.de,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] 3ware 5/6/7/8000 driver v1.26.02.000
Date: Fri, 10 Sep 2004 15:53:31 +0200 [thread overview]
Message-ID: <20040910135331.GA484@lst.de> (raw)
In-Reply-To: <I3R1V900.IHN@hadar.amcc.com>
On Wed, Sep 08, 2004 at 06:08:27PM -0700, Adam Radford wrote:
> Andrew/James/Christoph Hellwig,
>
> Here is a large driver update for the 3ware 5/6/7/8000 series controllers
> for 2.6.9-rc1-bk16.
>
> Changes in this release are the following:
>
> - Remove deprecated SCSI_IOCTL_SEND_COMMAND interface.
> - Remove deprecated /proc/scsi/3w-xxxx interface.
> - Convert entire driver to pci_driver format.
> - Remove all mdelays, replace w/msleep to fix possible watchdog
> timer issues.
> - Make all register accesses macros.
> - Remove all prototypes from header file, reorder functions to
> eliminate all prototypes but one.
> - Add sysfs 'queue_depth' setting attribute.
> - Add sysfs 'stats' attribute.
> - Fix spinlocks everywhere, remove tw_lock spinlock.
> - Remove all bitfields, add bitmask access macros.
> - Remove un-needed scsi_eh_abort entrypoint. Controller does not
> support aborting invididual IO's, scsi_eh_reset sufficient.
>
> The patch is rather lengthy due to the function reordering. I hope it doesn't
> get sniffed out by the list server.
The patch is indeed extremly huge and because of that not really
reviewable :P I did a quick look over the patched sourcefiles and
the driver looks pretty nice to me (except for the non-standard coding
style which we tend to accept if the diver is sane otherwise) and it
also compiles without a warning on ppc64.
Minor things (could be fixed in a followup patch)
- tw_check_bits should be marked static like everything else
- please provide a MODULE_VERSION like most modern scsi drivers
- in the ioctl path it might be usefull to use dma_alloc_coherent
instead of pci_alloc_consistent because it allows allocations to
sleep when use with GFP_KERNEL as last argument (else they're the
same on pci devices)
- also in the ioctl patch you return the value that copy_to_user
returned, but that's not an error code but the number of bytes
copied, you probaly want an
if (copy_to_user(argp, tw_ioctl, sizeof(TW_New_Ioctl) +
data_buffer_length - 1))
error = -EFAULT;
parent reply other threads:[~2004-09-10 13:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <I3R1V900.IHN@hadar.amcc.com>]
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=20040910135331.GA484@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=aradford@amcc.com \
--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 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).