From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/2] Extended attribute readahead
Date: Sun, 1 Nov 2015 20:02:57 +0100 [thread overview]
Message-ID: <1446404579-5211-1-git-send-email-agruenba@redhat.com> (raw)
Hello,
here are two patches that implement extended attribute readahead for those
cases where the extended attribute block is allocated immediately upon
inode creation (i.e., with SELinux or inherited permissions). The first
patch submits a READA request for the extended attributes after submitting
a READ request for the inode.
The second patch submits both requests in a single bio instead. As you can
see, this is somewhat messy. I'm not convinced that this optimization buys
us anything, so I will not recommend merging this patch.
Git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/agruen/linux.git gfs2-wip
Could you please review?
Thanks,
Andreas
Andreas Gruenbacher (2):
gfs2: Extended attribute readahead
gfs2: Extended attribute readahead optimization
fs/gfs2/dir.c | 15 ++++++---
fs/gfs2/incore.h | 1 +
fs/gfs2/meta_io.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++++++----
fs/gfs2/meta_io.h | 2 +-
fs/gfs2/quota.c | 2 +-
fs/gfs2/rgrp.c | 2 +-
fs/gfs2/super.c | 1 +
fs/gfs2/xattr.c | 10 +++---
8 files changed, 109 insertions(+), 19 deletions(-)
--
2.5.0
next reply other threads:[~2015-11-01 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 19:02 Andreas Gruenbacher [this message]
2015-11-01 19:02 ` [Cluster-devel] [PATCH 1/2] gfs2: Extended attribute readahead Andreas Gruenbacher
2015-11-03 17:29 ` Bob Peterson
2015-11-03 19:02 ` Steven Whitehouse
2015-11-03 20:18 ` Andreas Gruenbacher
2015-11-01 19:02 ` [Cluster-devel] [PATCH 2/2] gfs2: Extended attribute readahead optimization Andreas Gruenbacher
2015-11-12 13:44 ` Steven Whitehouse
2015-11-12 15:33 ` Andreas Gruenbacher
2015-11-12 20:15 ` Andreas Gruenbacher
2015-11-12 20:33 ` Steven Whitehouse
2015-11-13 22:24 ` Andreas Gruenbacher
2015-11-16 18:14 ` Bob Peterson
2015-11-13 13:48 ` Bob Peterson
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=1446404579-5211-1-git-send-email-agruenba@redhat.com \
--to=agruenba@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).