From: Dave Chinner <david@fromorbit.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Abhi Das <adas@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
cluster-devel <cluster-devel@redhat.com>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] fs: Add dirreadahead syscall and VFS hooks
Date: Thu, 31 Jul 2014 13:31:56 +1000 [thread overview]
Message-ID: <20140731033156.GQ26465@dastard> (raw)
In-Reply-To: <CAHO5Pa2fW6mZRTao3uEx2p_X9GvO1btrbb9Bg2ns94+p4biKAQ@mail.gmail.com>
On Tue, Jul 29, 2014 at 10:21:50AM +0200, Michael Kerrisk wrote:
> [CC+=linux-api]
>
> On Fri, Jul 25, 2014 at 7:37 PM, Abhi Das <adas@redhat.com> wrote:
> > Also adds a void *opaque field to struct dir_context that can be
> > used by filesystems to temporarily store any context as this
> > struct gets passed around in the fs.
So the prototype is:
int dir_readahead(int fd, off64_t offset, unsigned int count);
Why do we need a new syscall for this?
$ man 2 readahead
....
ssize_t readahead(int fd, off64_t offset, size_t count);
....
EINVAL fd does not refer to a file type to which readahead() can be applied.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-07-31 3:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:37 [RFC PATCH 0/2] dirreadahead system call Abhi Das
2014-07-25 17:37 ` [RFC PATCH 1/2] fs: Add dirreadahead syscall and VFS hooks Abhi Das
2014-07-29 8:21 ` Michael Kerrisk
2014-07-31 3:31 ` Dave Chinner [this message]
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-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=20140731033156.GQ26465@dastard \
--to=david@fromorbit.com \
--cc=adas@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.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