linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Layton, Evan J" <evan.j.layton@intel.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "Jelinek, Sarah" <sarah.jelinek@intel.com>
Subject: Triggering readpages operation
Date: Wed, 25 Jul 2012 19:59:26 +0000	[thread overview]
Message-ID: <CC35AC3D.1A5D%evan.j.layton@intel.com> (raw)


I'm working on a project at intel and working on a better understanding of "file system" operations specifically triggering readpages. However I have not been able to figure out how to drive or force the file system to use readpages. I had thought that readahead() would allow me to do this but it's not driving readpages and just goes down the readpage path. Any suggestions on the best way to get the file system to trigger this operation?

Thanks,
-evan

             reply	other threads:[~2012-07-25 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 19:59 Layton, Evan J [this message]
2012-07-26 11:32 ` Triggering readpages operation Jeff Layton
2012-07-26 19:51   ` Layton, Evan J

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=CC35AC3D.1A5D%evan.j.layton@intel.com \
    --to=evan.j.layton@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sarah.jelinek@intel.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).