From: jd <jpd_hp_linux_scsi@yahoo.com>
To: Jeff Garzik <jgarzik@pobox.com>, linux-scsi@vger.kernel.org
Subject: Re: 1st REVIEW : UNH iSCSI for 2.6-test5
Date: Fri, 26 Sep 2003 04:27:46 -0700 (PDT) [thread overview]
Message-ID: <20030926112746.95211.qmail@web60202.mail.yahoo.com> (raw)
In-Reply-To: <3F71C1CA.5030004@pobox.com>
--- Jeff Garzik <jgarzik@pobox.com> wrote:
> jd wrote:
> > Hi,
> >
> > Available for first Review & Comments.
> >
> > The UNH iSCSI Project, a collaborative effort between the
> > UNH IOL and Hewlett Packard Company in Austin, Texas,
> > ( hosted at http://sourceforge.net/projects/unh-iscsi )
> > to produce a full feature, generic iSCSI implementation ,
> > has ported the 2.4.18/20 version of the iSCSI initiator to
> > Linux 2.6.test5 Kernel for consideration of inclusion for
> > future distribution.
> >
> > A patch file is available for review at:
> >
> > http://www.parisc-linux.org/~jpd/
> >
> > Files included in the patch :
> >
> > drivers/scsi/Makefile
> > drivers/scsi/Kconfig
> > drivers/scsi/unh_iscsi
> > drivers/scsi/unh_iscsi/initiator # HBA & Data mover
> > drivers/scsi/unh_iscsi/common # Login and shared files
> > drivers/scsi/unh_iscsi/security $ SRP and CHAP login
> >
> > Please submit comments to :
> >
> > linux-scsi@vger.kernel.org
>
> Please don't mangle or otherwise use non-RFC email addresses. When
> you
> use your normal email address somewhere in the email _anyway_, you're
>
> annoying valid users while doing nothing to defeat spammers.
>
>
> comments:
>
> * use generic facility for crc32
>
> * most of the formatting looks good, but some of it looks crazy, like
>
> > + add_length = scan_table_and_process(sock,
> > + p_param_tbl,
> > + SECURITY_PARAM | INFORMATIONAL_PARAM,
> > + INITIATOR,
> > + inputpdu,
> > + outputpdu,
> > + connection_flags, login_flags);
>
> * indeed, this needs to be legible to people w/ 80-column screens
>
> * I disagree with the need for "my_kmalloc" and "my_kfree". Ditch
> the
> allocator and directly use the kernel counterparts.
>
> * function prototypes should use "u32" not "__u32" forms. Ditto for
> other kernel-internal structures.
>
> * string_llx is not needed. use sprintf.
>
> * verbosely dumping scsi ops is something that should be more generic
>
> (or removed)
>
> * authentication should be offloaded to a daemon, as NFSv4 did
>
> * I got tired of scrolling right to read code, at this point
>
Thanks for the feedback.
We're aleady aware of these issues ,
and unfortunately the first couple
of files in common/* that you got tired
of scrolling through will be eliminated
eventually anyway. ;) . They happen to
be shared with other components that are
not in consideration for inclusion.
John Donnelly.
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
next prev parent reply other threads:[~2003-09-26 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 15:12 1st REVIEW : UNH iSCSI for 2.6-test5 jd
2003-09-24 16:09 ` Jeff Garzik
2003-09-26 11:27 ` jd [this message]
2003-10-01 19:34 ` jd
2003-09-24 17:39 ` Christoph Hellwig
2003-09-24 17:48 ` Christoph Hellwig
2003-09-25 8:19 ` Christoph Hellwig
2003-09-26 11:17 ` jd
2003-10-01 19:19 ` 1st REVIEW : UNH iSCSI for 2.6-test5 - Questions jd
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=20030926112746.95211.qmail@web60202.mail.yahoo.com \
--to=jpd_hp_linux_scsi@yahoo.com \
--cc=jgarzik@pobox.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