From: Bean Huo <huobean@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, beanhuo@micron.com
Subject: Re: [PATCH RFC] mm: Let readahead submit larger batches of pages in case of ra->ra_pages == 0
Date: Fri, 11 Sep 2020 10:15:24 +0200 [thread overview]
Message-ID: <ef82be594709a8f954f4933968bd96888e589df3.camel@gmail.com> (raw)
In-Reply-To: <20200904110938.d9a2cb53a58e67a15c960f47@linux-foundation.org>
On Fri, 2020-09-04 at 11:09 -0700, Andrew Morton wrote:
> On Fri, 4 Sep 2020 16:48:07 +0200 Bean Huo <huobean@gmail.com>
> wrote:
>
> > From: Bean Huo <beanhuo@micron.com>
> >
> > Current generic_file_buffered_read() will break up the larger
> > batches of pages
> > and read data in single page length in case of ra->ra_pages == 0.
> > This patch is
> > to allow it to pass the batches of pages down to the device if the
> > supported
> > maximum IO size >= the requested size.
> >
> > ...
> >
> > --- a/mm/filemap.c
> > +++ b/mm/filemap.c
> > @@ -2062,6 +2062,7 @@ ssize_t generic_file_buffered_read(struct
> > kiocb *iocb,
> > struct file *filp = iocb->ki_filp;
> > struct address_space *mapping = filp->f_mapping;
> > struct inode *inode = mapping->host;
> > + struct backing_dev_info *bdi = inode_to_bdi(mapping->host);
> > struct file_ra_state *ra = &filp->f_ra;
> > loff_t *ppos = &iocb->ki_pos;
> > pgoff_t index;
> > @@ -2098,9 +2099,14 @@ ssize_t generic_file_buffered_read(struct
> > kiocb *iocb,
> > if (!page) {
> > if (iocb->ki_flags & IOCB_NOIO)
> > goto would_block;
> > - page_cache_sync_readahead(mapping,
> > - ra, filp,
> > - index, last_index - index);
> > +
> > + if (!ra->ra_pages && bdi->io_pages >=
> > last_index - index)
> > + __do_page_cache_readahead(mapping,
> > filp, index,
> > + last_index -
> > index, 0);
> > + else
> > + page_cache_sync_readahead(mapping, ra,
> > filp,
> > + index,
> > + last_index -
> > index);
> > page = find_get_page(mapping, index);
> > if (unlikely(page == NULL))
> > goto no_cached_page;
>
> I assume this is a performance patch. What are the observed changes
> in behaviour?
>
> What is special about ->ra_pages==0? Wouldn't this optimization
> still
> be valid if ->ra_pages==2?
>
> Doesn't this defeat the purpose of having ->ra_pages==0?
Hi Andrew
Sorry, I am still not quite understanding your above three questions.
Based on my shallow understanding, ra_pages is associated with
read_ahead_kb. Seems ra_pages controls the maximum read-ahead window
size, but it doesn't work when the requested size exceeds ra_pages.
If I set the read_ahead_kb to 0, also, as Christoph mentioned, MTD
forcibly sets ra_pages to 0. I think the intention is that only wants
to disable read-ahead, however, doesn't want
generic_file_buffered_read() to split the request and read data with
4KB chunk size separately.
Thanks,
Bean
next prev parent reply other threads:[~2020-09-11 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 14:48 Bean Huo
2020-09-04 18:09 ` Andrew Morton
2020-09-11 8:15 ` Bean Huo [this message]
2020-09-11 9:47 ` Christoph Hellwig
2020-09-11 11:35 ` Bean Huo
2020-09-11 11:36 ` Bean Huo
2020-09-07 7:16 ` Christoph Hellwig
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=ef82be594709a8f954f4933968bd96888e589df3.camel@gmail.com \
--to=huobean@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=beanhuo@micron.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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