From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
Konstantin Khelbnikov <khlebnikov@openvz.org>
Subject: Re: [PATCH] mm: move buffer_heads_over_limit check up
Date: Fri, 17 Feb 2012 18:41:23 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1202171823350.25244@eggly.anvils> (raw)
In-Reply-To: <20120217161142.a3ffa135.akpm@linux-foundation.org>
On Fri, 17 Feb 2012, Andrew Morton wrote:
>
> I don't think there's a lot of point in trying to micro-optimise the
> buffer_heads_over_limit==true case, either. But I suppose that
> pointlessly locking 1000000 anon pages is indeed pointless. Hopefully
> there _is_ a point in micro-optimising the actual test for
> buffer_heads_over_limit==true. So...
That's fine, yes, and thanks for putting this in. I just want to
exonerate Mel: it's not a fix to his useful work on buffer_heads_over_limit,
but I don't think he'll mind terribly that you've named it thus.
If it's a fix to anything, it's to my 3.3 free_hot_cold_page_list-ification
of shrink_active_list(), which was silly to leave the buffer_heads business
down there in move_active_pages_to_lru().
And the only reason I'm concerned to get it in, is that it's in an area
which I then trample over in the per-memcg per-zone locking series (as
is Hillf's rearrangement around update_isolated_counts()), so it's
convenient for me to have both of those in the base, instead of
having to put them in a prologue.
If I were to worry about the buffer_heads_over_limit situation itself,
I might worry about the unevictable pages which we never scan.
Hugh
>
> --- a/mm/vmscan.c~mm-vmscan-forcibly-scan-highmem-if-there-are-too-many-buffer_heads-pinning-highmem-fix-fix
> +++ a/mm/vmscan.c
> @@ -1723,11 +1723,12 @@ static void shrink_active_list(unsigned
> continue;
> }
>
> - if (buffer_heads_over_limit &&
> - page_has_private(page) && trylock_page(page)) {
> - if (page_has_private(page))
> - try_to_release_page(page, 0);
> - unlock_page(page);
> + if (unlikely(buffer_heads_over_limit)) {
> + if (page_has_private(page) && trylock_page(page)) {
> + if (page_has_private(page))
> + try_to_release_page(page, 0);
> + unlock_page(page);
> + }
> }
>
> if (page_referenced(page, 0, mz->mem_cgroup, &vm_flags)) {
> _
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-02-18 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 0:00 Hugh Dickins
2012-02-18 0:11 ` Andrew Morton
2012-02-18 2:41 ` Hugh Dickins [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=alpine.LSU.2.00.1202171823350.25244@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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