linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Vasilis Dimitsas <vdimitsas@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: asynchronous readahead prefetcher operation
Date: Thu, 13 Jul 2017 09:34:37 -0700	[thread overview]
Message-ID: <20170713163437.GA4469@bombadil.infradead.org> (raw)
In-Reply-To: <CAE=wTWYU8F5KDrC9VSxrtckVZ2xmvxy8owxCkZUcY4KXEiz0Og@mail.gmail.com>

On Wed, Jul 12, 2017 at 11:31:21PM +0300, Vasilis Dimitsas wrote:
> I am currently working on a project which is related to the operation of
> the linux readahead prefetcher. As a result, I am trying to understand its
> operation. Having read thoroughly the relevant part in the kernel code, I
> realize, from the comments, that part of the prefetching occurs
> asynchronously. The problem is that I can not verify this from the code.
> 
> Even if you call page_cache_sync_readahead() or
> page_cache_async_readahead(), then both will end up in ra_submit(), in
> which, the operation is common for both cases.
> 
> So, please could you tell me at which point does the operation of
> prefetching occurs asynchronously?

The prefetching operation always occurs asynchronously; the
I/O is submitted and then both page_cache_sync_readahead() and
page_cache_async_readahead() return to the caller.  They use slightly
different algorithms, which is why they're different functions, but the
I/O is not waited for.  It's up to the caller to do that.

I imagine you're looking at filemap_fault(), and it happens like this:

        page = find_get_page(mapping, offset);
(returns NULL because there's no page in the cache)
                do_sync_mmap_readahead(vmf->vma, ra, file, offset);
(will create pages and put them in the page cache, taking PageLock on each page)
                page = find_get_page(mapping, offset);
(finds the page that was just created)
        if (!lock_page_or_retry(page, vmf->vma->vm_mm, vmf->flags)) {
(will attempt to lock the page ... if it's locked and the fault lets us retry,
fails so we can handle retries at the higher level.  If it's locked and the
fault says we can't retry, then sleeps until unlocked.  If/once it's unlocked,
will return success)

When the I/O completes, the page will be unlocked, usually by calling
page_endio().

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-07-13 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 20:31 asynchronous readahead prefetcher operation Vasilis Dimitsas
2017-07-13 16:34 ` Matthew Wilcox [this message]
2017-07-13 20:36   ` Vasilis Dimitsas
2017-07-14  1:55     ` Matthew Wilcox

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=20170713163437.GA4469@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=vdimitsas@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;
as well as URLs for NNTP newsgroup(s).