From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mhocko@suse.com" <mhocko@suse.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] mm: Generalize putback scan functions
Date: Fri, 15 Feb 2019 17:13:36 -0500 [thread overview]
Message-ID: <20190215221335.32zqxhwtcr2kmgku@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <b2fcd214-52a5-6284-81b9-8a09de27fbea@virtuozzo.com>
On Fri, Feb 15, 2019 at 10:01:05PM +0000, Kirill Tkhai wrote:
> On 15.02.2019 23:39, Daniel Jordan wrote:
> > On Thu, Feb 14, 2019 at 01:35:37PM +0300, Kirill Tkhai wrote:
> >> +static unsigned noinline_for_stack move_pages_to_lru(struct lruvec *lruvec,
> >> + struct list_head *list)
> >> {
> >> struct pglist_data *pgdat = lruvec_pgdat(lruvec);
> >> + int nr_pages, nr_moved = 0;
> >> LIST_HEAD(pages_to_free);
> >> + struct page *page;
> >> + enum lru_list lru;
> >>
> >> - /*
> >> - * Put back any unfreeable pages.
> >> - */
> >> - while (!list_empty(page_list)) {
> >> - struct page *page = lru_to_page(page_list);
> >> - int lru;
> >> -
> >> + while (!list_empty(list)) {
> >> + page = lru_to_page(list);
> >> VM_BUG_ON_PAGE(PageLRU(page), page);
> >> - list_del(&page->lru);
> >> if (unlikely(!page_evictable(page))) {
> >> + list_del_init(&page->lru);
> >
> > Why change to list_del_init? It's more special than list_del but doesn't seem
> > needed since the page is list_add()ed later.
>
> Not something special is here, I'll remove this _init.
>
> > That postprocess script from patch 1 seems kinda broken before this series, and
> > still is. Not that it should block this change. Out of curiosity did you get
> > it to run?
>
> I fixed all new warnings, which come with my changes, so the patch does not make
> the script worse.
>
> If you change all already existing warnings by renaming variables in appropriate
> places, the script will work in some way. But I'm not sure this is enough to get
> results correct, and I have no a big wish to dive into perl to fix warnings
> introduced by another people, so I don't plan to do with this script something else.
Ok, was asking in case I was doing something wrong.
With the above change, for the series, you can add
Reviewed-by: Daniel Jordan <daniel.m.jordan@oracle.com>
next prev parent reply other threads:[~2019-02-15 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 10:35 [PATCH v2 0/4] mm: Generalize putback functions Kirill Tkhai
2019-02-14 10:35 ` [PATCH v2 1/4] mm: Move recent_rotated pages calculation to shrink_inactive_list() Kirill Tkhai
2019-02-14 20:57 ` Andrew Morton
2019-02-15 7:38 ` [PATCH v2.5 " Kirill Tkhai
2019-02-14 10:35 ` [PATCH v2 2/4] mm: Move nr_deactivate accounting to shrink_active_list() Kirill Tkhai
2019-02-14 10:35 ` [PATCH v2 3/4] mm: Remove pages_to_free argument of move_active_pages_to_lru() Kirill Tkhai
2019-02-14 10:35 ` [PATCH v2 4/4] mm: Generalize putback scan functions Kirill Tkhai
2019-02-15 20:39 ` Daniel Jordan
2019-02-15 22:01 ` Kirill Tkhai
2019-02-15 22:13 ` Daniel Jordan [this message]
2019-02-18 8:20 ` Kirill Tkhai
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=20190215221335.32zqxhwtcr2kmgku@ca-dmjordan1.us.oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
/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