[Stgt-devel] User-mode iSER

FUJITA Tomonori fujita.tomonori
Mon Aug 7 00:25:50 CEST 2006

From: "Alexander Nezhinsky" <nezhinsky at gmail.com>
Subject: Re: [Stgt-devel] User-mode iSER
Date: Sun, 6 Aug 2006 20:41:16 +0300

> But anyway, I meant primarily the modes of operation that are not
> file-system related.
> For example, with etx3 sync'ing the journal is clearly  the kind of
> "application-related" operation that needs an explicit flush/barrier.
> My question was mainly related to the cases when no such need occurs
> naturally.
> What if the user works with the raw unpartitioned device -- does he still
> get a guarantee of correct operation under failures? And if it is done
> through sg driver (not through the block device subsystem)?
> Do you imply that if the devices are reported as write-back (plus capable of
> performing flushes etc) then the problem is solved even if the cache is
> de-facto volatile?

As I said in the first mail, modern applications can enjoy writeback
cache. If your applications are not modern, that is, does not know a
proper way to use writeback cache, just configure your disc drive to
use write-through.

By the way, please don't use html mails. I will not reply next time.

More information about the stgt mailing list