Linux-Fsdevel Archive on
help / color / mirror / Atom feed
From: David Howells <>
To: Matthew Wilcox <>
Subject: Re: [PATCH] afs: Don't unlock fetched data pages until the op completes successfully
Date: Sun, 17 May 2020 23:36:57 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Matthew Wilcox <> wrote:

> > +	if (req->page_done)
> > +		for (req->index = 0; req->index < req->nr_pages; req->index++)
> > +			req->page_done(req);
> > +
> I'd suggest doing one call rather than N and putting the page iteration
> inside the callback.  But this patch is appropriate for this late in
> the -rc series, just something to consider for the future.

My rewrite of the fscache stuff changes this bit of the code anyway, and makes
it one call which may start a write out to the cache.


      parent reply	other threads:[~2020-05-17 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 20:21 David Howells
2020-05-17 21:08 ` Matthew Wilcox
2020-05-17 22:36 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] afs: Don'\''t unlock fetched data pages until the op completes successfully' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).