From: Michal Hocko <mhocko@kernel.org>
To: Kuo-Hsin Yang <vovoy@chromium.org>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-mm@kvack.org, Chris Wilson <chris@chris-wilson.co.uk>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>
Subject: Re: [PATCH v4] mm, drm/i915: mark pinned shmemfs pages as unevictable
Date: Mon, 5 Nov 2018 14:02:09 +0100 [thread overview]
Message-ID: <20181105130209.GI4361@dhcp22.suse.cz> (raw)
In-Reply-To: <20181105111348.182492-1-vovoy@chromium.org>
On Mon 05-11-18 19:13:48, Kuo-Hsin Yang wrote:
> The i915 driver uses shmemfs to allocate backing storage for gem
> objects. These shmemfs pages can be pinned (increased ref count) by
> shmem_read_mapping_page_gfp(). When a lot of pages are pinned, vmscan
> wastes a lot of time scanning these pinned pages. In some extreme case,
> all pages in the inactive anon lru are pinned, and only the inactive
> anon lru is scanned due to inactive_ratio, the system cannot swap and
> invokes the oom-killer. Mark these pinned pages as unevictable to speed
> up vmscan.
>
> Export pagevec API check_move_unevictable_pages().
Thanks for reworking the patch. This looks much more to my taste. At
least the mm part. I haven't really looked at the the drm part.
Just a nit below
> This patch was inspired by Chris Wilson's change [1].
>
> [1]: https://patchwork.kernel.org/patch/9768741/
I would recommend using msg-id based url.
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Dave Hansen <dave.hansen@intel.com>
> Signed-off-by: Kuo-Hsin Yang <vovoy@chromium.org>
other than that
Acked-by: Michal Hocko <mhocko@suse.com>
[...]
> @@ -4184,15 +4185,13 @@ int page_evictable(struct page *page)
>
> #ifdef CONFIG_SHMEM
> /**
> - * check_move_unevictable_pages - check pages for evictability and move to appropriate zone lru list
> - * @pages: array of pages to check
> - * @nr_pages: number of pages to check
> + * check_move_unevictable_pages - move evictable pages to appropriate evictable
> + * lru lists
I am not sure this is an improvement. I would just keep the original
wording. It is not great either but the explicit note about check for
evictability sounds like a better fit to me.
> + * @pvec: pagevec with pages to check
> *
> - * Checks pages for evictability and moves them to the appropriate lru list.
> - *
> - * This function is only used for SysV IPC SHM_UNLOCK.
> + * This function is only used to move shmem pages.
I do not really see anything that would be shmem specific here. We can
use this function for any LRU pages unless I am missing something
obscure. I would just drop the last sentence.
A note that this function should be only used for LRU pages would be
nice.
> */
> -void check_move_unevictable_pages(struct page **pages, int nr_pages)
> +void check_move_unevictable_pages(struct pagevec *pvec)
> {
> struct lruvec *lruvec;
> struct pglist_data *pgdat = NULL;
> @@ -4200,8 +4199,8 @@ void check_move_unevictable_pages(struct page **pages, int nr_pages)
> int pgrescued = 0;
> int i;
>
> - for (i = 0; i < nr_pages; i++) {
> - struct page *page = pages[i];
> + for (i = 0; i < pvec->nr; i++) {
> + struct page *page = pvec->pages[i];
> struct pglist_data *pagepgdat = page_pgdat(page);
>
> pgscanned++;
> @@ -4233,4 +4232,5 @@ void check_move_unevictable_pages(struct page **pages, int nr_pages)
> spin_unlock_irq(&pgdat->lru_lock);
> }
> }
> +EXPORT_SYMBOL(check_move_unevictable_pages);
> #endif /* CONFIG_SHMEM */
> --
> 2.19.1.930.g4563a0d9d0-goog
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-11-05 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 11:13 Kuo-Hsin Yang
2018-11-05 13:02 ` Michal Hocko [this message]
2018-11-05 13:05 ` Michal Hocko
2018-11-05 14:33 ` Kuo-Hsin Yang
2018-11-05 16:41 ` Michal Hocko
2018-11-06 0:03 ` Kuo-Hsin Yang
2018-11-05 18:52 ` Dave Hansen
2018-11-06 0:04 ` Kuo-Hsin Yang
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=20181105130209.GI4361@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=dave.hansen@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=vovoy@chromium.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