From: David Howells <dhowells@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: dhowells@redhat.com, Jeff Layton <jlayton@kernel.org>,
Marc Dionne <marc.dionne@auristor.com>,
Ilya Dryomov <idryomov@gmail.com>,
linux-afs@lists.infradead.org, ceph-devel@vger.kernel.org,
linux-cachefs@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] netfs, afs, ceph: Use folios
Date: Thu, 12 Aug 2021 21:47:54 +0100 [thread overview]
Message-ID: <3308343.1628801274@warthog.procyon.org.uk> (raw)
In-Reply-To: <YRVHLu3OAwylCONm@casper.infradead.org>
Matthew Wilcox <willy@infradead.org> wrote:
> > (*) Can page_endio() be split into two separate functions, one for read
> > and one for write? If seems a waste of time to conditionally switch
> > between two different branches.
>
> At this point I'm thinking ...
>
> static inline void folio_end_read(struct folio *folio, int err)
> {
> if (!err)
> folio_set_uptodate(folio);
> folio_unlock(folio);
> }
>
> Clearly the page isn't uptodate at this point, or ->readpage wouldn't've
> been called. So there's no need to clear it. And PageError is
> completely useless.
Seems reasonable.
> > - *_page = page;
> > + *_page = &folio->page;
>
> Can't do anything about this one; the write_begin API needs to be fixed.
That's fine. I expected things like this at this stage.
> > @@ -174,40 +175,32 @@ static void afs_kill_pages(struct address_space *mapping,
> [...]
> > + folio_clear_uptodate(folio);
> > + folio_end_writeback(folio);
> > + folio_lock(folio);
> > + generic_error_remove_page(mapping, &folio->page);
> > + folio_unlock(folio);
> > + folio_put(folio);
>
> This one I'm entirely missing. It's awkward. I'll work on it.
afs_kill_pages() is just a utility to end writeback, clear uptodate and do
generic_error_remove_page() over a range of pages and afs_redirty_pages() is a
utility that to end writeback and redirty a range of pages - hence why I was
thinking it might make sense to put them into common code.
> > - index += thp_nr_pages(page);
> > - if (!pagevec_add(&pvec, page))
> > + index += folio_nr_pages(folio);
> > + if (!pagevec_add(&pvec, &folio->page))
>
> Pagevecs are also awkward. I haven't quite figured out how to
> transition them to folios.
Maybe provide pagevec_add_folio(struct pagevec *, struct folio *)?
> > zero_out:
> > - zero_user_segments(page, 0, offset, offset + len, thp_size(page));
> > + zero_user_segments(&folio->page, 0, offset, offset + len, folio_size(folio));
>
> Yeah, that's ugly.
Maybe:
folio_clear_around(folio, keep_from, keep_to);
clearing the bits of the folio outside the specified section?
David
prev parent reply other threads:[~2021-08-12 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 13:07 David Howells
2021-08-11 13:54 ` Matthew Wilcox
2021-08-11 21:05 ` [RFC][PATCH] afs: Use folios in directory handling David Howells
2021-08-12 16:07 ` [RFC][PATCH] netfs, afs, ceph: Use folios Matthew Wilcox
2021-08-13 6:53 ` Christoph Hellwig
2021-08-13 8:17 ` David Howells
2021-08-12 20:47 ` David Howells [this message]
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=3308343.1628801274@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marc.dionne@auristor.com \
--cc=willy@infradead.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