public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@suse.de>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Hannes Reinecke <hare@suse.de>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 3/3 version 4] scsi_lib: Collapse scsi_end_request into only user
Date: Tue, 05 Jan 2010 18:23:56 +0200	[thread overview]
Message-ID: <4B43679C.9090009@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1001051014200.3002-100000@iolanthe.rowland.org>

On 01/05/2010 05:20 PM, Alan Stern wrote:
> On Tue, 5 Jan 2010, Boaz Harrosh wrote:
> 
>> Embedding scsi_end_request() into scsi_io_completion actually simplifies
>> the code and makes it clearer what's going on.
>>
>> There is absolutely no functional and/or side effects changes after this
>> patch.
> 
> Here are some suggestions for changes to the comments.  These are quite
> minor and you might not want to bother updating the patch yet again...
> 

Sure, NP. thanks for checking me out, coming from Hebrew I do need support
in these matters. Will update tomorrow.

Alan can I add your Review-by: this time around?

>> +	if (likely(0 == blk_end_request(req, error, good_bytes))) {
>> +		/* All is done and good move to next command */
> 
> 		/* The command completed successfully; move on to the next. */
> 
>> +		cmd->request = NULL;
>> +		action = ACTION_NEXT_CMND;
>> +	} else if (result == 0) {
>> +		/* Wrote some bytes but request was split */
> 
> 		/* The command was successful but not all the data was
> 		 * transferred; re-prep the command to handle the rest.
> 		 */
> 
>> +		action = ACTION_REPREP;
>> +	} else if (error && scsi_noretry_cmd(cmd)) {
>> +		/* kill remainder if no retries */
> 
> 		/* Error.  Kill the request since retries are disallowed. */
> 
>> +		blk_end_request_all(req, error);
>> +		cmd->request = NULL;
>> +		action = ACTION_NEXT_CMND;
>> +	} else if (host_byte(result) == DID_RESET) {
> 
> Alan Stern
> 

Thanks
Boaz

  reply	other threads:[~2010-01-05 16:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 12:11 [PATCHSET 0/3] little bit of love to scsi_io_completion Boaz Harrosh
2010-01-04 12:13 ` [PATCH 1/3] scsi_lib: request_queue is only needed inside scsi_requeue_command Boaz Harrosh
2010-01-04 12:15 ` [PATCH 2/3] scsi_lib: Remove that __scsi_release_buffers contraption Boaz Harrosh
2010-01-04 12:17 ` [PATCH 3/3] scsi_lib: Collapse scsi_end_request into only user Boaz Harrosh
2010-01-04 13:23   ` Matthew Wilcox
2010-01-04 13:56     ` Boaz Harrosh
2010-01-04 14:07   ` [PATCH 3/3 version 2] " Boaz Harrosh
2010-01-04 14:12     ` Boaz Harrosh
2010-01-04 18:23     ` Alan Stern
2010-01-05  7:27       ` Boaz Harrosh
2010-01-05  7:53     ` [PATCH 3/3 version 3] " Boaz Harrosh
2010-01-05  8:49       ` Boaz Harrosh
2010-01-05  9:07   ` [PATCH 3/3 version 4] " Boaz Harrosh
2010-01-05 15:20     ` Alan Stern
2010-01-05 16:23       ` Boaz Harrosh [this message]
2010-01-05 16:33         ` Alan Stern

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=4B43679C.9090009@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@suse.de \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=stern@rowland.harvard.edu \
    /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