From: David Hildenbrand <david@redhat.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: akpm@linux-foundation.org, mhocko@suse.com,
dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/2] mm, memory_hotplug: cleanup memory offline path
Date: Thu, 4 Apr 2019 16:47:43 +0200 [thread overview]
Message-ID: <7874ef85-adc7-95a8-87f4-1f15eb21c677@redhat.com> (raw)
In-Reply-To: <20190404132506.kaqzop4qs6m56plu@d104.suse.de>
On 04.04.19 15:25, Oscar Salvador wrote:
> On Thu, Apr 04, 2019 at 03:18:00PM +0200, David Hildenbrand wrote:
>>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>>> index f206b8b66af1..d8a3e9554aec 100644
>>> --- a/mm/memory_hotplug.c
>>> +++ b/mm/memory_hotplug.c
>>> @@ -1451,15 +1451,11 @@ static int
>>> offline_isolated_pages_cb(unsigned long start, unsigned long nr_pages,
>>> void *data)
>>> {
>>> - __offline_isolated_pages(start, start + nr_pages);
>>> - return 0;
>>> -}
>>> + unsigned long offlined_pages;
>>>
>>> -static void
>>> -offline_isolated_pages(unsigned long start_pfn, unsigned long end_pfn)
>>> -{
>>> - walk_system_ram_range(start_pfn, end_pfn - start_pfn, NULL,
>>> - offline_isolated_pages_cb);
>>> + offlined_pages = __offline_isolated_pages(start, start + nr_pages);
>>> + *(unsigned long *)data += offlined_pages;
>>
>> unsigned long *offlined_pages = data;
>>
>> *offlined_pages += __offline_isolated_pages(start, start + nr_pages);
>
> Yeah, more readable.
>
>> Only nits
>
> About the identation, I double checked the code and it looks fine to me.
> In [1] looks fine too, might be your mail client?
>
> [1] https://patchwork.kernel.org/patch/10885571/
Double checked, alignment on the parameter on the new line is very weird.
And both lines cross 80 lines per line ... nit :)
>
>>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>
> Thanks ;-)
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-04-04 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 12:59 [PATCH 0/2] Preparing memhotplug for allocating memmap from hot-added range Oscar Salvador
2019-04-04 12:59 ` [PATCH 1/2] mm, memory_hotplug: cleanup memory offline path Oscar Salvador
2019-04-04 13:18 ` David Hildenbrand
2019-04-04 13:25 ` Oscar Salvador
2019-04-04 14:47 ` David Hildenbrand [this message]
2019-04-04 15:40 ` Oscar Salvador
2019-04-04 16:50 ` David Hildenbrand
2019-04-04 12:59 ` [PATCH 2/2] mm, memory_hotplug: provide a more generic restrictions for memory hotplug Oscar Salvador
2019-04-04 14:57 ` David Hildenbrand
2019-04-04 15:02 ` David Hildenbrand
2019-04-04 18:01 ` Oscar Salvador
2019-04-04 18:27 ` David Hildenbrand
2019-04-05 7:14 ` Michal Hocko
2019-04-05 8:05 ` David Hildenbrand
2019-04-05 10:30 ` Michal Hocko
2019-04-05 10:56 ` David Hildenbrand
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=7874ef85-adc7-95a8-87f4-1f15eb21c677@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
/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