From: Michal Hocko <mhocko@suse.com>
To: Li Wang <liwang@redhat.com>
Cc: Zi Yan <zi.yan@cs.rutgers.edu>,
linux-mm@kvack.org, ltp@lists.linux.it,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [RFC PATCH] mm: correct status code which move_pages() returns for zero page
Date: Wed, 18 Apr 2018 13:29:16 +0200 [thread overview]
Message-ID: <20180418112916.GX17484@dhcp22.suse.cz> (raw)
In-Reply-To: <CAEemH2evD8Gk6y_q41ygBZVwu--U9oKvnPh8xsrb5R27oLCBDA@mail.gmail.com>
On Wed 18-04-18 18:39:19, Li Wang wrote:
> On Wed, Apr 18, 2018 at 5:19 PM, Michal Hocko <mhocko@suse.com> wrote:
>
> > On Wed 18-04-18 11:07:22, Michal Hocko wrote:
> > > On Tue 17-04-18 16:09:33, Zi Yan wrote:
> > [...]
> > > > diff --git a/mm/migrate.c b/mm/migrate.c
> > > > index f65dd69e1fd1..32afa4723e7f 100644
> > > > --- a/mm/migrate.c
> > > > +++ b/mm/migrate.c
> > > > @@ -1619,6 +1619,8 @@ static int do_pages_move(struct mm_struct *mm,
> > nodemask_t task_nodes,
> > > > if (err)
> > > > goto out;
> > > > }
> > > > + /* Move to next page (i+1), after we have saved page
> > status (until i) */
> > > > + start = i + 1;
> > > > current_node = NUMA_NO_NODE;
> > > > }
> > > > out_flush:
> > > >
> > > > Feel free to check it by yourselves.
> > >
> > > Yes, you are right. I never update start if the last page in the range
> > > fails and so we overwrite the whole [start, i] range. I wish the code
> > > wasn't that ugly and subtle but considering how we can fail in different
> > > ways and that we want to batch as much as possible I do not see an easy
> > > way.
> > >
> > > Care to send the patch? I would just drop the comment.
> >
> > Hmm, thinking about it some more. An alternative would be to check for
> > list_empty on the page list. It is a bit larger diff but maybe that
> > would be tiny bit cleaner because there is simply no point to call
> > do_move_pages_to_node on an empty list in the first place.
> >
>
> a??Hi Michal, Zi
>
> I tried your patch separately, both of them works fine to me.
Thanks for retesting! Do you plan to post a patch with the changelog or
should I do it?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-18 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 11:06 Li Wang
2018-04-17 13:03 ` Michal Hocko
2018-04-17 14:14 ` Michal Hocko
2018-04-17 14:28 ` Li Wang
2018-04-17 19:00 ` Michal Hocko
2018-04-17 20:09 ` Zi Yan
2018-04-18 9:07 ` Michal Hocko
2018-04-18 9:19 ` Michal Hocko
2018-04-18 10:39 ` Li Wang
2018-04-18 11:29 ` Michal Hocko [this message]
2018-04-18 11:46 ` Li Wang
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=20180418112916.GX17484@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=zi.yan@cs.rutgers.edu \
/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