From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/2] gfs2: Extended attribute readahead
Date: Tue, 3 Nov 2015 12:29:15 -0500 (EST) [thread overview]
Message-ID: <1797651004.2591857.1446571755023.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1446404579-5211-2-git-send-email-agruenba@redhat.com>
----- Original Message -----
> When gfs2 allocates an inode and its extended attribute block next to
> each other at inode create time, the inode's directory entry indicates
> that in de_rahead. In that case, we can readahead the extended
> attribute block when we read in the inode.
>
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
> ---
> fs/gfs2/dir.c | 15 +++++++++++----
> fs/gfs2/incore.h | 1 +
> fs/gfs2/meta_io.c | 27 +++++++++++++++++++++++++--
> 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, 46 insertions(+), 14 deletions(-)
>
Hi Andreas,
Most of this looks good. However, two comments:
1. I don't like adding a new u16 to the gfs2_inode. I've been working to
reduce the size of gfs2's inodes lately, so I'd rather see this
implemented as a new GIF_RAHEAD (or similar) flag in gfs2_inode's i_flags.
2. It seems to me like we should take advantage of function gfs2_meta_ra()
which already submits one block and a variable number of additional
blocks for read-ahead, then waits for the first block IO to complete.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2015-11-03 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 19:02 [Cluster-devel] [PATCH 0/2] Extended attribute readahead Andreas Gruenbacher
2015-11-01 19:02 ` [Cluster-devel] [PATCH 1/2] gfs2: " Andreas Gruenbacher
2015-11-03 17:29 ` Bob Peterson [this message]
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=1797651004.2591857.1446571755023.JavaMail.zimbra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.