On Tue, Apr 6, 2021 at 5:03 AM Gerald Schaefer <gerald.schaefer@xxxxxxxxxxxxx> wrote: > > On Thu, 1 Apr 2021 13:10:49 -0700 > Yang Shi <shy828301@xxxxxxxxx> wrote: > > [...] > > > > > > > > Yes, it could be. The old behavior of migration was to return -ENOMEM > > > > if THP migration is not supported then split THP. That behavior was > > > > not very friendly to some usecases, for example, memory policy and > > > > migration lieu of reclaim (the upcoming). But I don't mean we restore > > > > the old behavior. We could split THP if it returns -ENOSYS and the > > > > page is THP. > > > > > > OK, as long as we don't get any broken PMD migration entries established > > > for s390, some extra THP splitting would be acceptable I guess. > > > > There will be no migration PMD installed. The current behavior is a > > no-op if THP migration is not supported. > > Ok, just for completeness, since Mel also replied that the split > was not done on other architectures "because the loss from splitting > exceeded the gain of improved locality": > > I did not mean to request extra splitting functionality for s390, > simply skipping / ignoring large PMDs would also be fine for s390, > no need to add extra complexity. Thank you. It could make life easier. The current code still converts huge PMD to RPOTNONE even though THP migration is not supported. It is easy to skip such PMDs hence cycles are saved for pointless NUMA hinting page faults. Will do so in v2 if no objection from Mel as well.
