From: swhiteho@redhat.com <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Patches to add extent allocation to GFS2
Date: Wed, 6 Feb 2008 10:17:51 +0000 [thread overview]
Message-ID: <12022930761645-git-send-email-swhiteho@redhat.com> (raw)
This is a set of five patches which together add extent allocation to
GFS2. Also there is a bit of preliminary clean-up which results in
reducing the size of a gfs2_inode and merging some functions which
were almost identical.
The plan is to change gfs2's bmap functions next to take advantage
of these changes to improve performance, particularly with large
(i.e. multi-page) writes.
Steve.
next reply other threads:[~2008-02-06 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 10:17 swhiteho [this message]
2008-02-06 10:17 ` [Cluster-devel] [PATCH 1/5] [GFS2] Reduce inode size by merging fields swhiteho
2008-02-06 10:17 ` [Cluster-devel] [PATCH 2/5] [GFS2] Merge the rd_last_alloc_meta and rd_last_alloc_data fields swhiteho
2008-02-06 10:17 ` [Cluster-devel] [PATCH 3/5] [GFS2] Update gfs2_trans_add_unrevoke to accept extents swhiteho
2008-02-06 10:17 ` [Cluster-devel] [PATCH 4/5] [GFS2] Merge gfs2_alloc_meta and gfs2_alloc_data swhiteho
2008-02-06 10:17 ` [Cluster-devel] [PATCH 5/5] [GFS2] Add extent allocation to block allocator swhiteho
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=12022930761645-git-send-email-swhiteho@redhat.com \
--to=swhiteho@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).