public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <tluben@rogers.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi-misc-2.5 user per-device spare command
Date: Fri, 25 Apr 2003 14:36:33 -0400	[thread overview]
Message-ID: <3EA98031.2040108@rogers.com> (raw)
In-Reply-To: <20030425110002.A9928@beaverton.ibm.com>

Patrick Mansfield wrote:
> On Fri, Apr 25, 2003 at 01:45:58PM -0400, Luben Tuikov wrote:
> 
>>Patrick Mansfield wrote:
> 
> 
>>No, it is NOT different, because I can see your patch deleting
>>the good code which currently impements just that.
>>
>>All we want is for IO to keep going.  It does, so leave it alone.
> 
> 
> It is not clear that the IO will always make forward progress.

It is -- we have one spare per host, which will be used
when the cache fails.

10 When a commands completes, we will keep going.
20 If no command completes then there's something wrong with
the LLDD or the device, in which case the EH will grab it back.
GOTO 10
 
>>>>2. Why spare_cmd is a pointer? Why? Why?
>>>>Wouldn't it be much more *flexible* to be a list_head,
>>>>so that maybe we can hook up more commands in the future?
>>>>I.e. keep your options open...
>>>
>>>
>>>When or if we use more than one spare we can change the code to a
>>>list_head. I don't plan to add such code, so I see no reason to use a
>>>list_head.
>>
>>Yeah, and then you're going to change a WHOLE bunch of code
>>everywhere.
> 
> 
> No, maybe a few lines, maybe less code than is needed to actually
> support dyanmically changing the number of spared/cached commands.

The whole point is where to draw the line -- I say that
free_list is a good thing and free_ptr is a bad thing.
 
>>It's good not to overengineer, but it's even BETTER to know
>>when to do so and when to NOT do so.
> 
> Well we should never overengineer, but the term is subjective.

No, not never. The point is knowing when to do so and when not to do so.
 
>>Ideally, commands come out of cache/free_list, travel through
>>lists as they go about SCSI Core, and go back to the cache/free_list.
>>
>>So the following axiom: scsi command always belongs to a list.
> 
> 
> If they are freed (into cache), they are not on any list.

This is absolutely irrelevant.

BTW, did you really think that *that* was my point???

Just use your imagination... (next time)

(Patterns, consistency, etc.)

-- 
Luben












  reply	other threads:[~2003-04-25 18:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 17:02 [PATCH] scsi-misc-2.5 remove scsi_device list_lock Patrick Mansfield
2003-04-24 17:03 ` [PATCH] scsi-misc-2.5 user per-device spare command Patrick Mansfield
2003-04-24 17:03   ` [PATCH] scsi-misc-2.5 fold scsi_alloc_cmd into __scsi_get_command Patrick Mansfield
2003-04-25 10:12   ` [PATCH] scsi-misc-2.5 user per-device spare command Christoph Hellwig
2003-04-25 14:12     ` Luben Tuikov
2003-04-25 16:50       ` Patrick Mansfield
2003-04-25 16:56         ` Christoph Hellwig
2003-04-25 17:45         ` Luben Tuikov
2003-04-25 18:00           ` Patrick Mansfield
2003-04-25 18:36             ` Luben Tuikov [this message]
2003-04-25 16:37     ` Patrick Mansfield
2003-04-25 16:50       ` Christoph Hellwig
2003-04-25 16:57       ` James Bottomley
2003-04-25 20:49         ` Patrick Mansfield
2003-04-25 17:38       ` Luben Tuikov
2003-04-25 10:12 ` [PATCH] scsi-misc-2.5 remove scsi_device list_lock Christoph Hellwig
2003-04-25 10:47   ` Jens Axboe
2003-04-25 16:53     ` Patrick Mansfield
2003-04-25 17:20       ` Jens Axboe
2003-04-25 14:00   ` Luben Tuikov

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=3EA98031.2040108@rogers.com \
    --to=tluben@rogers.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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