From: Steven Whitehouse <swhiteho@redhat.com>
To: linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Subject: GFS2: Pre-pull patch posting (merge window)
Date: Mon, 1 Jul 2013 10:33:03 +0100 [thread overview]
Message-ID: <1372671195-3472-1-git-send-email-swhiteho@redhat.com> (raw)
Hi,
There are a few bug fixes for various, mostly very minor corner
cases, plus some interesting new features. The new features
include atomic_open whose main benefit will be the reduction in
locking overhead in case of combined lookup/create and open operations,
sorting the log buffer lists by block number to improve the efficiency
of AIL writeback, and agressively issuing revokes in gfs2_log_flush
to reduce overhead when dropping glocks,
Steve.
next reply other threads:[~2013-07-01 9:59 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 9:33 Steven Whitehouse [this message]
2013-07-01 9:33 ` [PATCH 01/12] GFS2: Sort buffer lists by inplace block number Steven Whitehouse
2013-07-01 9:33 ` [PATCH 02/12] GFS2: Eliminate gfs2_rg_lops Steven Whitehouse
2013-07-01 9:33 ` [PATCH 03/12] GFS2: Cocci spatch "ptr_ret.spatch" Steven Whitehouse
2013-07-01 9:33 ` [PATCH 04/12] GFS2: Remove no-op wrapper function Steven Whitehouse
2013-07-01 9:33 ` [PATCH 05/12] GFS2: fix error propagation in init_threads() Steven Whitehouse
2013-07-01 9:33 ` [PATCH 06/12] GFS2: Only do one directory search on create Steven Whitehouse
2013-07-01 9:33 ` [PATCH 07/12] GFS2: Add atomic_open support Steven Whitehouse
2013-07-01 9:33 ` [PATCH 08/12] GFS2: fix regression in dir_double_exhash Steven Whitehouse
2013-07-01 9:33 ` [PATCH 09/12] GFS2: aggressively issue revokes in gfs2_log_flush Steven Whitehouse
2013-07-01 9:33 ` [PATCH 10/12] GFS2: fix warning message Steven Whitehouse
2013-07-01 9:33 ` [PATCH 11/12] GFS2: Fix fstrim boundary conditions Steven Whitehouse
2013-07-01 9:33 ` [PATCH 12/12] GFS2: Reserve journal space for quota change in do_grow Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 9:53 GFS2: Pre-pull patch posting (merge window) Steven Whitehouse
2014-06-03 11:02 Steven Whitehouse
2014-04-01 9:15 Steven Whitehouse
2014-01-20 12:23 Steven Whitehouse
2013-11-04 11:09 Steven Whitehouse
2013-09-05 9:02 GFS2 " Steven Whitehouse
2013-04-26 9:18 GFS2: " Steven Whitehouse
2013-02-19 10:07 Steven Whitehouse
2012-11-30 9:52 Steven Whitehouse
2012-09-26 8:25 Steven Whitehouse
2012-07-23 8:00 Steven Whitehouse
2012-05-17 12:23 Steven Whitehouse
2012-03-19 10:25 Steven Whitehouse
2012-03-19 14:45 ` Randy Dunlap
2012-03-19 14:59 ` Steven Whitehouse
2012-03-19 15:18 ` Randy Dunlap
2012-03-19 15:34 ` Steven Whitehouse
2012-03-23 19:41 ` David Teigland
2012-03-23 19:46 ` David Miller
2012-03-23 20:06 ` Randy Dunlap
2012-03-23 20:09 ` Steven Whitehouse
2012-03-23 20:18 ` David Teigland
2012-03-23 22:06 ` Benjamin Poirier
2012-03-23 22:48 ` Randy Dunlap
2012-03-26 10:44 ` Steven Whitehouse
2012-04-02 15:35 ` Randy Dunlap
2012-04-02 15:47 ` Steven Whitehouse
2012-03-23 22:06 ` Randy Dunlap
2012-03-20 9:47 ` Steven Whitehouse
2012-01-05 11:51 Steven Whitehouse
2011-10-24 12:48 Steven Whitehouse
2011-07-22 9:16 Steven Whitehouse
2011-05-19 8:46 Steven Whitehouse
2011-03-15 9:11 Steven Whitehouse
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=1372671195-3472-1-git-send-email-swhiteho@redhat.com \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®