This patch updates text in SCST README about barriers usage Signed-off-by: Vladislav Bolkhovitin <vst@xxxxxxxx> README | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) Index: scst/README =================================================================== --- scst/README (revision 641) +++ scst/README (working copy) @@ -607,12 +607,11 @@ IMPORTANT: By default for performance re On Linux initiators for EXT3 and ReiserFS file systems the barrier protection could be turned on using "barrier=1" and "barrier=flush" mount options correspondingly. Note, that - usually it turned off by default and the status of barriers - usage isn't reported anywhere in the system logs as well as - there is no way to know it on the mounted file system (at - least no known one). Windows and, AFAIK, other UNIX'es don't - need any special explicit options and do necessary barrier - actions on write-back caching devices by default. Also note + usually it's turned off by default (see http://lwn.net/Articles/283161). + You can check if it's turn on or off by looking in /proc/mounts. + Windows and, AFAIK, other UNIX'es don't need any special + explicit options and do necessary barrier actions on + write-back caching devices by default. Also note that on some real-life workloads write through caching might perform better, than write back one with the barrier protection turned on. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
