From: Chris Goldsworthy <cgoldswo@codeaurora.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, david@redhat.com
Subject: Re: [PATCH] fs/buffer.c: Revoke LRU when trying to drop buffers
Date: Tue, 05 Jan 2021 06:57:26 -0800 [thread overview]
Message-ID: <fe8c287dcd131a573ae4b7a46a36825e@codeaurora.org> (raw)
In-Reply-To: <20201124153912.GC4327@casper.infradead.org>
On 2020-11-24 07:39, Matthew Wilcox wrote:
> On Mon, Nov 23, 2020 at 10:49:38PM -0800, Chris Goldsworthy wrote:
>> +static void __evict_bh_lru(void *arg)
>> +{
>> + struct bh_lru *b = &get_cpu_var(bh_lrus);
>> + struct buffer_head *bh = arg;
>> + int i;
>> +
>> + for (i = 0; i < BH_LRU_SIZE; i++) {
>> + if (b->bhs[i] == bh) {
>> + brelse(b->bhs[i]);
>> + b->bhs[i] = NULL;
>> + goto out;
>
> That's an odd way to spell 'break' ...
>
>> + }
>> + }
>> +out:
>> + put_cpu_var(bh_lrus);
>> +}
>
> ...
>
>> @@ -3245,8 +3281,15 @@ drop_buffers(struct page *page, struct
>> buffer_head **buffers_to_free)
>>
>> bh = head;
>> do {
>> - if (buffer_busy(bh))
>> - goto failed;
>> + if (buffer_busy(bh)) {
>> + /*
>> + * Check if the busy failure was due to an
>> + * outstanding LRU reference
>> + */
>> + evict_bh_lrus(bh);
>> + if (buffer_busy(bh))
>> + goto failed;
Hi Matthew,
Apologies for the delayed response.
> We might be better off just calling invalidate_bh_lrus() -- we'd flush
> the entire LRU, but we'd only need to do it once, not once per buffer
> head.
I'm concerned about emptying the cache, such that those who might
benefit
from it would be left affected.
> We could have a more complex 'evict' that iterates each busy buffer on
> a
> page so transforming:
>
> for_each_buffer
> for_each_cpu
> for_each_lru_entry
>
> to:
>
> for_each_cpu
> for_each_buffer
> for_each_lru_entry
>
> (and i suggest that way because it's more expensive to iterate the
> buffers
> than it is to iterate the lru entries)
I've gone ahead and done this in a follow-up patch:
https://lore.kernel.org/lkml/cover.1609829465.git.cgoldswo@codeaurora.org/
There might be room for improvement in the data structure being used to
track the used entries - using an xarray gives the cleanest code, but
pre-allocating an array to hold up to page_size(page) / bh->b_size
entres
might be faster, although it would be a bit uglier to do in a way that
doesn't reduce the performance of the case when evict_bh_lru() doesn't
need to be called.
Regards,
Chris.
--
The Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2021-01-05 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 6:49 [PATCH] Resolve LRU page-pinning issue for file-backed pages Chris Goldsworthy
2020-11-24 6:49 ` [PATCH] fs/buffer.c: Revoke LRU when trying to drop buffers Chris Goldsworthy
2020-11-24 15:39 ` Matthew Wilcox
2021-01-05 14:57 ` Chris Goldsworthy [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=fe8c287dcd131a573ae4b7a46a36825e@codeaurora.org \
--to=cgoldswo@codeaurora.org \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.