On Thu, Oct 21, 2021 at 02:35:32PM +0200, David Hildenbrand wrote: > My opinion after all the discussions: use a dedicate type with a clear > name to solve the immediate filemap API issue. Leave the remainder alone > for now. Less code to touch, less subsystems to involve (well, still a > lot), less people to upset, less discussions to have, faster review, > faster upstream, faster progress. A small but reasonable step. I don't get it. I mean I'm not the MM expert, I've only been touching most areas of it occasionally for the last 20 years, but anon and file pages have way more in common both in terms of use cases and implementation than what is different (unlike some of the other (ab)uses of struct page). What is the point of splitting it now when there are tons of use cases where they are used absolutely interchangable both in consumers of the API and the implementation?
