From: Christoph Hellwig <hch@infradead.org>
To: "Smart, James" <James.Smart@Emulex.Com>
Cc: Linux SCSI Reflector <linux-scsi@vger.kernel.org>
Subject: Re: [Emulex] Ready for next round...
Date: Wed, 16 Jun 2004 09:31:42 +0100 [thread overview]
Message-ID: <20040616083142.GA8757@infradead.org> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF28034F94D5@xbl.ma.emulex.com>
On Tue, Jun 15, 2004 at 01:32:56PM -0400, Smart, James wrote:
> Christoph, et al...
>
> I'd like to request the next round of review comments on the driver.
>
> We believe that tonights posting on SourceForge has addressed all of the
> comments to date with only a couple of exceptions (see below).
Okay, here's a review vs the original comments:
> - your module_param usage is b0rked. Instead of duplicating every
> option 31 times use module_param_array. You also seem to miss
> the paramter descriptions (MODULE_PARAM_DESC)
Your paramters are still extremly crappy. lpfc.conf is horrible, as is
having the module paramters in a header. What's especially bad is that
they are character paramters without any abvious reasons, please use
the proper integer types.
lpfc_cfgparm.h is truely horrible.
> - lpfc_clock.c should go away, just use add_timer/etc. diretly and
> embedd the timer into your structures. Yes, I know that's not
> how SVR4-derivates work, but Linux does. You also have an
> unchecked kmalloc and a list_head cast in there..
Still not much better. In fact the crappy datastructures and code are
still there, just spread all over the place now instead of fixed up.
> - dito for lpfc_sysfs_info_show, in short all your sysfs work is completely
> wrong, also you seem to use driver attributes instead of scsi device/host
> attributes. why?
You're still attaching all the attributes yourself. Please use the
scsi-provided host/device attributes instead.
> - the lpfc_find_target usage in queuecommand looks bogus. You have
> scsi_device->hostdata to put per-lun data, from which you can trivially
> link per-target data directly. All the checks for inquiry and valid
> luns are similarly b0rked - scsi probing works by calling ->slave_alloc
> first so you'll a) have a place where you know the midlayer is probing
> and b) always private data when quecommand is called.
While you started using sdev->hostdata the whole code is still more than
fishy. You have a complete set of secondary data structures for target/lun
data lookup yet. Please allocate all per-lun data in ->slave_alloc and
if the target data doesn't exist yet that one too and hang it off the lun
data.
next prev parent reply other threads:[~2004-06-16 8:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 17:32 [Emulex] Ready for next round Smart, James
2004-06-16 8:17 ` Christoph Hellwig
2004-06-16 13:35 ` Jamie Wellnitz
2004-06-16 13:50 ` Christoph Hellwig
2004-06-16 8:20 ` Christoph Hellwig
2004-06-16 8:31 ` Christoph Hellwig [this message]
2004-06-20 13:35 ` Christoph Hellwig
2004-06-23 15:31 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 19:56 Smart, James
2004-06-18 20:58 ` 'Christoph Hellwig'
2004-07-09 19:24 Smart, James
2004-07-09 22:08 ` 'Christoph Hellwig'
2004-07-09 22:10 ` 'Christoph Hellwig'
2004-07-17 11:26 Smart, James
2004-07-17 20:17 ` 'Christoph Hellwig'
2004-07-17 20:26 ` 'Christoph Hellwig'
2004-07-19 20:02 Ely, Paul
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=20040616083142.GA8757@infradead.org \
--to=hch@infradead.org \
--cc=James.Smart@Emulex.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