From: Christoph Hellwig <hch@infradead.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v5 04/13] mm: Add readahead address space operation
Date: Wed, 12 Feb 2020 10:18:11 -0800 [thread overview]
Message-ID: <20200212181811.GC9756@infradead.org> (raw)
In-Reply-To: <20200211010348.6872-5-willy@infradead.org>
On Mon, Feb 10, 2020 at 05:03:39PM -0800, Matthew Wilcox wrote:
> +struct readahead_control {
> + struct file *file;
> + struct address_space *mapping;
> +/* private: use the readahead_* accessors instead */
> + pgoff_t start;
> + unsigned int nr_pages;
> + unsigned int batch_count;
We often use __ prefixes for the private fields to make that a little
more clear.
next prev parent reply other threads:[~2020-02-12 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200211010348.6872-1-willy@infradead.org>
[not found] ` <20200211010348.6872-3-willy@infradead.org>
2020-02-12 18:13 ` [Ocfs2-devel] [PATCH v5 02/13] mm: Ignore return value of ->readpages Christoph Hellwig
[not found] ` <20200211010348.6872-7-willy@infradead.org>
2020-02-13 22:09 ` [Ocfs2-devel] [PATCH v5 06/13] fs: Convert mpage_readpages to mpage_readahead Junxiao Bi
[not found] ` <20200211010348.6872-4-willy@infradead.org>
2020-02-14 3:36 ` [Ocfs2-devel] [PATCH v5 03/13] mm: Put readahead pages in cache earlier John Hubbard
2020-02-15 1:15 ` Matthew Wilcox
[not found] ` <20200211010348.6872-5-willy@infradead.org>
2020-02-11 4:52 ` [Ocfs2-devel] [PATCH v5 04/13] mm: Add readahead address space operation Dave Chinner
[not found] ` <20200211125413.GU8731@bombadil.infradead.org>
2020-02-11 20:08 ` Dave Chinner
2020-02-12 18:18 ` Christoph Hellwig [this message]
2020-02-14 5:36 ` John Hubbard
2020-02-15 1:15 ` Matthew Wilcox
[not found] ` <20200211010348.6872-2-willy@infradead.org>
2020-02-12 18:13 ` [Ocfs2-devel] [PATCH v5 01/13] mm: Fix the return type of __do_page_cache_readahead Christoph Hellwig
2020-02-14 3:19 ` John Hubbard
2020-02-14 4:21 ` Matthew Wilcox
2020-02-14 4:33 ` John Hubbard
2020-02-14 19:50 ` 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=20200212181811.GC9756@infradead.org \
--to=hch@infradead.org \
--cc=ocfs2-devel@oss.oracle.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