mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kenny Simpson <theonetruekenny@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Kenny Simpson <theonetruekenny@yahoo.com>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: RE: RAID controller safety
Date: Fri, 6 Jan 2006 07:18:55 -0800 (PST)	[thread overview]
Message-ID: <20060106151855.63846.qmail@web34102.mail.mud.yahoo.com> (raw)
In-Reply-To: <1136558807.30498.24.camel@localhost.localdomain>

--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Gwe, 2006-01-06 at 09:33 -0500, Salyzyn, Mark wrote:
> > The dpt_i2o driver (which is a scsi driver) accepts the
> > SYNCHRONIZE_CACHE scsi command and passes it off to the firmware. The
> > firmware respects this and flushes all the outstanding (cached)
> > commands. This is true in all (kernel.org or Adaptec latest) versions.
> 
> In which case it should be fine and correct with the generic i2o_scsi as
> well as that will pass through SCSI command requests directly. i2o_block
> doesn't know about converting any incoming cache flush to an i2o command
> block so might not.
> 
> Alan
> 

Won't the i2o_block driver use i2o_block_device_flush to flush the devices' cache (by issuing a
I2O_CMD_BLOCK_CFLUSH), or this this function used in some very different context?

Oddly enough, I see I2O_CMD_BLOCK_CFLISH #define'd to 0x37 in both the i2o driver
(include/linux/i2o.h), AND in the dpt driver (drivers/scsi/dpt/dpti_i2o.h).  However, I do not see
the dpt driver using this value anywhere.

-Kenny



		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 


  reply	other threads:[~2006-01-06 15:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 14:33 Salyzyn, Mark
2006-01-06 14:46 ` Alan Cox
2006-01-06 15:18   ` Kenny Simpson [this message]
2006-01-06 16:02     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2006-01-06 17:06 Salyzyn, Mark
2005-12-29 16:29 Kenny Simpson
2005-12-30 15:17 ` Alan Cox
2005-12-30 16:18   ` Kenny Simpson
2005-12-30 18:20     ` Alan Cox
2005-12-30 18:58       ` Kenny Simpson
2005-12-30 19:31         ` Bernd Eckenfels
2005-12-31  0:49         ` Alan Cox
2005-12-31  3:25           ` Kenny Simpson
2005-12-31  3:29           ` Kenny Simpson
2005-12-31  6:55           ` Kenny Simpson
2005-12-31  7:57           ` Kenny Simpson

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=20060106151855.63846.qmail@web34102.mail.mud.yahoo.com \
    --to=theonetruekenny@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.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

all inboxes | Powered by JetHome®