From: Keith Mannthey <kmannth@us.ibm.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Barriers per second while doing Odirect Random Writes
Date: Mon, 26 Apr 2010 00:06:17 -0700 [thread overview]
Message-ID: <1272265577.9664.57.camel@keith-laptop> (raw)
Ted and all,
While using this FFSB test profile:
http://btrfs.boxacle.net/repository/raid/2010-04-14_2004//ext4-2.6.34-rc3-nobarrier//btrfs1.ffsb.random_writes_odirect__threads_0128.10-04-21_17.38.39/benchmark/profile
(The profile is 128 threads of all odirect random writes. )
on my raid box I am seeing (via Darricks block_barrier tracepoint) right
about 32 barriers per second.
Initial analysis using perf shows kdmflush as the cause. I will continue
to look into this.
Thanks,
Keith Mannthey
LTC FS-Dev
reply other threads:[~2010-04-26 7:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1272265577.9664.57.camel@keith-laptop \
--to=kmannth@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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