From: Andrew Morton <akpm@osdl.org>
To: arjanv@redhat.com
Cc: axboe@suse.de, mason@suse.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext3 barrier bits
Date: Sat, 22 May 2004 01:33:13 -0700 [thread overview]
Message-ID: <20040522013313.6cb15a4b.akpm@osdl.org> (raw)
In-Reply-To: <1085214261.2781.1.camel@laptop.fenrus.com>
Arjan van de Ven <arjanv@redhat.com> wrote:
>
>
> > - Does the kernel tell you if your disk doesn't supoprt barriers? ie:
> > how does the user know if it's working or not?
>
> ... and how do you know your disk isn't lying and ignoring the barriers?
>
If some benchmark slows down when barriers are enabled then that's a pretty
good indicator. I don't know what benchmark that might be though.
next prev parent reply other threads:[~2004-05-22 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040521093207.GA1952@suse.de>
[not found] ` <20040521023807.0de63c7a.akpm@osdl.org>
[not found] ` <20040521100234.GK1952@suse.de>
[not found] ` <20040521235044.6160cccb.akpm@osdl.org>
[not found] ` <20040522073540.GO1952@suse.de>
2004-05-22 8:11 ` [PATCH] ext3 barrier bits Andrew Morton
2004-05-22 8:24 ` Arjan van de Ven
2004-05-22 8:33 ` Andrew Morton [this message]
2004-05-22 19:15 ` Chris Mason
2004-05-22 8:43 ` Jens Axboe
2004-05-22 8:42 ` Jens Axboe
2004-05-22 19:31 ` Chris Mason
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=20040522013313.6cb15a4b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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