From: Abhi Das <adas@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
cluster-devel@redhat.com
Subject: [RFC PATCH 0/2] dirreadahead system call
Date: Fri, 25 Jul 2014 12:37:29 -0500 [thread overview]
Message-ID: <1406309851-10628-1-git-send-email-adas@redhat.com> (raw)
This system call takes 3 arguments:
fd - file descriptor of the directory being readahead
*offset - offset in dir from which to resume. This is updated
as we move along in the directory
count - The max number of entries to readahead
The syscall is supposed to read upto 'count' entries starting at
'*offset' and cache the inodes corresponding to those entries. It
returns a negative error code or a positive number indicating
the number of inodes it has issued readaheads for. It also
updates the '*offset' value so that repeated calls to dirreadahead
can resume at the right location. Returns 0 when there are no more
entries left.
Abhi Das (2):
fs: Add dirreadahead syscall and VFS hooks
gfs2: GFS2's implementation of the dir_readahead file operation
arch/x86/syscalls/syscall_32.tbl | 1 +
arch/x86/syscalls/syscall_64.tbl | 1 +
fs/gfs2/Makefile | 3 +-
fs/gfs2/dir.c | 49 ++++++---
fs/gfs2/dir.h | 15 +++
fs/gfs2/dir_readahead.c | 209 +++++++++++++++++++++++++++++++++++++++
fs/gfs2/file.c | 2 +
fs/gfs2/main.c | 10 +-
fs/gfs2/super.c | 1 +
fs/readdir.c | 49 +++++++++
include/linux/fs.h | 3 +
11 files changed, 328 insertions(+), 15 deletions(-)
create mode 100644 fs/gfs2/dir_readahead.c
--
1.8.1.4
next reply other threads:[~2014-07-25 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:37 Abhi Das [this message]
2014-07-25 17:37 ` [RFC PATCH 1/2] fs: Add dirreadahead syscall and VFS hooks Abhi Das
[not found] ` <1406309851-10628-2-git-send-email-adas-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-29 8:21 ` Michael Kerrisk
[not found] ` <CAHO5Pa2fW6mZRTao3uEx2p_X9GvO1btrbb9Bg2ns94+p4biKAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-31 3:31 ` Dave Chinner
2014-07-25 17:37 ` [RFC PATCH 2/2] gfs2: GFS2's implementation of the dir_readahead file operation Abhi Das
2014-07-26 5:27 ` [RFC PATCH 0/2] dirreadahead system call Andreas Dilger
2014-07-28 12:52 ` Abhijith Das
2014-07-28 21:19 ` Andreas Dilger
2014-07-29 9:36 ` [Cluster-devel] " Steven Whitehouse
2014-07-31 4:49 ` Dave Chinner
2014-07-31 11:19 ` Andreas Dilger
2014-07-31 23:53 ` Dave Chinner
2014-08-01 2:11 ` Abhijith Das
2014-08-01 5:54 ` Andreas Dilger
2014-08-06 2:01 ` Dave Chinner
2014-10-21 5:21 ` Abhijith Das
2014-11-10 3:41 ` Abhijith Das
2014-11-10 22:23 ` Andreas Dilger
2014-11-10 22:47 ` Abhijith Das
2014-08-01 9:14 ` Thomas Martitz
2014-07-29 8:19 ` Michael Kerrisk
2014-07-31 3:18 ` NeilBrown
2014-08-01 2:21 ` Abhijith Das
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=1406309851-10628-1-git-send-email-adas@redhat.com \
--to=adas@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).