From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: cache+barriers vs cache+nobarriers vs disabled cache+barriers vs disabled cache+nobarriers
Date: Thu, 15 Mar 2007 14:07:34 +0100 [thread overview]
Message-ID: <200703151407.34419.Martin@lichtvoll.de> (raw)
In-Reply-To: <200703151339.36259.Martin@lichtvoll.de>
Am Donnerstag 15 März 2007 schrieb Martin Steigerwald:
> But why do you want to disable write cache in the first case? As long
> as you are using 2.6.17.7 or later you can safely enable barriers and
> and write cache.
Hello again, Leon,
of couse using write barriers is only possible if the hardware
requirements (cache flushes or similar mechanisms) are met. XFS complains
if it can't use barriers. See dmesg or log for details.
It seems that the mailinglist software broke my GPG signature. It was
correct as I sent out the mail.
Regards,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2007-03-15 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 9:16 cache+barriers vs cache+nobarriers vs disabled cache+barriers vs disabled cache+nobarriers Leon Kolchinsky
2007-03-15 12:39 ` Martin Steigerwald
2007-03-15 13:07 ` Martin Steigerwald [this message]
2007-03-18 10:07 ` Leon Kolchinsky
2007-03-18 21:33 ` Chris Wedgwood
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=200703151407.34419.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-xfs@oss.sgi.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