[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86536aa5-8e9a-64ec-1bee-c47ee24fc683@redhat.com>
Date: Fri, 3 Sep 2021 09:31:28 +0200
From: David Hildenbrand <david@...hat.com>
To: Peter Xu <peterx@...hat.com>, linux-mm@...ck.org,
Hugh Dickins <hughd@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Cc: Miaohe Lin <linmiaohe@...wei.com>,
Matthew Wilcox <willy@...radead.org>,
Yang Shi <shy828301@...il.com>,
"Kirill A . Shutemov" <kirill@...temov.name>,
Jerome Glisse <jglisse@...hat.com>,
Alistair Popple <apopple@...dia.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2 5/5] mm: Add ZAP_FLAG_SKIP_SWAP and zap_flags
>> @@ -3377,7 +3377,7 @@ void unmap_mapping_pages(struct address_space *mapping, pgoff_t start,
>> pgoff_t nr, bool even_cows)
>> {
>> pgoff_t first_index = start, last_index = start + nr - 1;
>> - struct zap_details details = { };
>> + struct zap_details details = { .zap_flags = ZAP_FLAG_SKIP_SWAP };
>>
>> details.zap_mapping = even_cows ? NULL : mapping;
>> if (last_index < first_index)
>>
>
> I think what would really help is to add a high-level description what
> unmap_mapping_page() vs. unmap_mapping_pages() really does, and what the
> expectations/use cases are. The names are just way too similar ...
aaaaand staring only at this patch I missed that we have nice
descriptions already :)
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists