From: Pasha Tatashin <Pavel.Tatashin@microsoft.com> To: Oscar Salvador <osalvador@techadventures.net>, "akpm@linux-foundation.org" <akpm@linux-foundation.org> Cc: "mhocko@suse.com" <mhocko@suse.com>, "dan.j.williams@intel.com" <dan.j.williams@intel.com>, "david@redhat.com" <david@redhat.com>, "Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>, "yasu.isimatu@gmail.com" <yasu.isimatu@gmail.com>, "malat@debian.org" <malat@debian.org>, "linux-mm@kvack.org" <linux-mm@kvack.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Oscar Salvador <osalvador@suse.de> Subject: Re: [PATCH 3/5] mm/memory_hotplug: Tidy up node_states_clear_node Date: Thu, 20 Sep 2018 23:40:39 +0000 [thread overview] Message-ID: <73bf94f3-d53b-0123-0b1e-86fd00f66694@microsoft.com> (raw) In-Reply-To: <20180919100819.25518-4-osalvador@techadventures.net> On 9/19/18 6:08 AM, Oscar Salvador wrote: > From: Oscar Salvador <osalvador@suse.de> > > node_states_clear has the following if statements: > > if ((N_MEMORY != N_NORMAL_MEMORY) && > (arg->status_change_nid_high >= 0)) > ... > > if ((N_MEMORY != N_HIGH_MEMORY) && > (arg->status_change_nid >= 0)) > ... > > N_MEMORY can never be equal to neither N_NORMAL_MEMORY nor > N_HIGH_MEMORY. > > Similar problem was found in [1]. > Since this is wrong, let us get rid of it. > > [1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fpatch%2F10579155%2F&data=02%7C01%7CPavel.Tatashin%40microsoft.com%7C1e31e6a5c8754abe0b4608d61e17e01c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636729485241367584&sdata=ztkPNyRIv2c0j5lrujwGM%2FrD5in6G7AvvdqxVXCzwGs%3D&reserved=0 > > Signed-off-by: Oscar Salvador <osalvador@suse.de> Reviewed-by: Pavel Tatashin <pavel.tatashin@microsoft.com> > --- > mm/memory_hotplug.c | 6 ++---- > 1 file changed, 2 insertions(+), 4 deletions(-) > > diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c > index c2c7359bd0a7..131c08106d54 100644 > --- a/mm/memory_hotplug.c > +++ b/mm/memory_hotplug.c > @@ -1590,12 +1590,10 @@ static void node_states_clear_node(int node, struct memory_notify *arg) > if (arg->status_change_nid_normal >= 0) > node_clear_state(node, N_NORMAL_MEMORY); > > - if ((N_MEMORY != N_NORMAL_MEMORY) && > - (arg->status_change_nid_high >= 0)) > + if (arg->status_change_nid_high >= 0) > node_clear_state(node, N_HIGH_MEMORY); > > - if ((N_MEMORY != N_HIGH_MEMORY) && > - (arg->status_change_nid >= 0)) > + if (arg->status_change_nid >= 0) > node_clear_state(node, N_MEMORY); > } > >
next prev parent reply other threads:[~2018-09-20 23:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-19 10:08 [PATCH 0/5] Refactor node_states_check_changes_online/offline Oscar Salvador 2018-09-19 10:08 ` [PATCH 1/5] mm/memory_hotplug: Spare unnecessary calls to node_set_state Oscar Salvador 2018-09-20 20:53 ` Pasha Tatashin 2018-09-19 10:08 ` [PATCH 2/5] mm/memory_hotplug: Avoid node_set/clear_state(N_HIGH_MEMORY) when !CONFIG_HIGHMEM Oscar Salvador 2018-09-20 20:59 ` Pasha Tatashin 2018-09-21 10:31 ` Oscar Salvador 2018-09-19 10:08 ` [PATCH 3/5] mm/memory_hotplug: Tidy up node_states_clear_node Oscar Salvador 2018-09-20 23:40 ` Pasha Tatashin [this message] 2018-09-19 10:08 ` [PATCH 4/5] mm/memory_hotplug: Simplify node_states_check_changes_online Oscar Salvador 2018-09-21 0:15 ` Pasha Tatashin 2018-09-21 10:30 ` Oscar Salvador 2018-09-19 10:08 ` [PATCH 5/5] mm/memory_hotplug: Clean up node_states_check_changes_offline Oscar Salvador 2018-09-21 0:38 ` Pasha Tatashin
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=73bf94f3-d53b-0123-0b1e-86fd00f66694@microsoft.com \ --to=pavel.tatashin@microsoft.com \ --cc=Jonathan.Cameron@huawei.com \ --cc=akpm@linux-foundation.org \ --cc=dan.j.williams@intel.com \ --cc=david@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=malat@debian.org \ --cc=mhocko@suse.com \ --cc=osalvador@suse.de \ --cc=osalvador@techadventures.net \ --cc=yasu.isimatu@gmail.com \ --subject='Re: [PATCH 3/5] mm/memory_hotplug: Tidy up node_states_clear_node' \ /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
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.