From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/3] GFS2: More performance patches
Date: Mon, 16 Sep 2013 15:10:41 -0500 [thread overview]
Message-ID: <1379362244-5477-1-git-send-email-rpeterso@redhat.com> (raw)
Hi,
Here's another set of 3 performance patches for GFS2. The patches are:
[GFS2 PATCH 1/3] GFS2: Eliminate a goto from function
[GFS2 PATCH 2/3] GFS2: Drop initial reservation if too small
[GFS2 PATCH 3/3] GFS2: Don't insert into reservations tree unless
You may recall that with the previous set of 5 patches, I ran postmark
and achieved this result:
852.13 megabytes written (971.69 kilobytes per second)
With this latest set of 3 patches, it's even more efficient:
852.13 megabytes written (1.05 megabytes per second)
which is about 8% faster.
Regards,
Bob Peterson
Red Hat File Systems
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
reply other threads:[~2013-09-16 20:10 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=1379362244-5477-1-git-send-email-rpeterso@redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).