public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Nicholas A. Bellinger" <nick@pyxtechnologies.com>
Cc: iscsi-initiator-core-announce@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>,
	iscsi-initiator-core-devel
	<iscsi-initiator-core-devel@iscsi-initiator-core.org>,
	Christoph Hellwig <hch@lst.de>, Mike Christie <mikenc@us.ibm.com>
Subject: Re: [ANNOUNCE] iscsi-initiator-core 1.6.2.0-rc1 for 2.6.12-rc1
Date: Sat, 23 Apr 2005 21:49:15 -0500	[thread overview]
Message-ID: <1114310956.4805.9.camel@mulgrave> (raw)
In-Reply-To: <1112385701.3008.18.camel@haakon>

On Fri, 2005-04-01 at 12:01 -0800, Nicholas A. Bellinger wrote:
> A few minor fixes in this release, with the main feature addition being
> support for persistent connection/session parameters as defined within 
> /etc/sysconfig/initiator.  For example, it is now possible to define
> specific connection/session parameters and have those values remain
> throughout connection/session failures.  Also, the first run of tests
> with dm-multipath have been compelted successful.  I am working on a
> section within the documentation to describe how these two pieces work
> together within linux 2.6.
> 
> Also an important milestone has been reached with v1.0 of the
> iscsi-initiator-core.org howto located at:
> 
> http://iscsi-initiator-core.org/mediawiki/index.php/Howto
> 
> This is a work in progress as data is imported from the ASCII version
> from iscsi-initiator-core-tools v2.3.
> 
> This release is now considered stable and no new features will be added
> until 1.6.2.0-final is released.

OK, I assessed this for inclusion.

The feedback I had based on my last review was

1) Use the iscsi transport class
2) get rid of MC/S in favour of dm-multipath
3) Don't try to subvert the SCSI error handler

Point 3) is much better, but still present in this:

+	/*
+	 * This is completion of a given struct scsi_cmnd after an
+	 * iSCSI exception occured.  Based upon iSCSI exceptions and/or
+	 * passed action parameter, struct scsi_cmnd->eh_timeout may have
+	 * been stopped, and needs to be rstarted before completion to
+	 * the SCSI stack.
+	 */
+	if (!(timer_pending(&sc->eh_timeout))) {
+		sc->eh_timeout.data = (unsigned long) sc;
+		sc->eh_timeout.expires = (jiffies + sc->timeout_per_command);
+		sc->eh_timeout.function = scsi_timeout_function;
+		add_timer(&sc->eh_timeout);

However the other two still have not been addressed, so this patch is
not suitable for inclusion.

James



  reply	other threads:[~2005-04-24  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 20:01 [ANNOUNCE] iscsi-initiator-core 1.6.2.0-rc1 for 2.6.12-rc1 Nicholas A. Bellinger
2005-04-24  2:49 ` James Bottomley [this message]
2005-04-26  0:00   ` Nicholas A. Bellinger

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=1114310956.4805.9.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=hch@lst.de \
    --cc=iscsi-initiator-core-announce@vger.kernel.org \
    --cc=iscsi-initiator-core-devel@iscsi-initiator-core.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikenc@us.ibm.com \
    --cc=nick@pyxtechnologies.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