On Mon, 8 Feb 2021 02:27:06 +0000 Song Bao Hua (Barry Song) wrote: > > On Sun, Feb 07, 2021 at 10:24:28PM +0000, Song Bao Hua (Barry Song) wrote: > > > > > In high-performance I/O cases, accelerators might want to perform > > > > > I/O on a memory without IO page faults which can result in dramatically > > > > > increased latency. Current memory related APIs could not achieve this > > > > > requirement, e.g. mlock can only avoid memory to swap to backup device, > > > > > page migration can still trigger IO page fault. > > > > > > > > Well ... we have two requirements. The application wants to not take > > > > page faults. The system wants to move the application to a different > > > > NUMA node in order to optimise overall performance. Why should the > > > > application's desires take precedence over the kernel's desires? And why > > > > should it be done this way rather than by the sysadmin using numactl to > > > > lock the application to a particular node? > > > > > > NUMA balancer is just one of many reasons for page migration. Even one > > > simple alloc_pages() can cause memory migration in just single NUMA > > > node or UMA system. > > > > > > The other reasons for page migration include but are not limited to: > > > * memory move due to CMA > > > * memory move due to huge pages creation > > > > > > Hardly we can ask users to disable the COMPACTION, CMA and Huge Page > > > in the whole system. > > > > You're dodging the question. Should the CMA allocation fail because > > another application is using SVA? > > > > I would say no. > > I would say no as well. > > While IOMMU is enabled, CMA almost has one user only: IOMMU driver > as other drivers will depend on iommu to use non-contiguous memory > though they are still calling dma_alloc_coherent(). > > In iommu driver, dma_alloc_coherent is called during initialization > and there is no new allocation afterwards. So it wouldn't cause > runtime impact on SVA performance. Even there is new allocations, > CMA will fall back to general alloc_pages() and iommu drivers are > almost allocating small memory for command queues. > > So I would say general compound pages, huge pages, especially > transparent huge pages, would be bigger concerns than CMA for > internal page migration within one NUMA. > > Not like CMA, general alloc_pages() can get memory by moving > pages other than those pinned. > > And there is no guarantee we can always bind the memory of > SVA applications to single one NUMA, so NUMA balancing is > still a concern. > > But I agree we need a way to make CMA success while the userspace > pages are pinned. Since pin has been viral in many drivers, I > assume there is a way to handle this. Otherwise, APIs like > V4L2_MEMORY_USERPTR[1] will possibly make CMA fail as there > is no guarantee that usersspace will allocate unmovable memory > and there is no guarantee the fallback path- alloc_pages() can > succeed while allocating big memory. > > Will investigate more. > > > The application using SVA should take the one-time > > performance hit from having its memory moved around. > > Sometimes I also feel SVA is doomed to suffer from performance > impact due to page migration. But we are still trying to > extend its use cases to high-performance I/O. Because of the double edges an usual sword has, the chance seems zero for you to rake in IO performance on the left side with nobody hurt on the other side. And the good news is mempinfd takes care of things like CAP_IPC_LOCK, and like any sysctl available, the double edge dilemma can be worked out in the user space.
