On Wed, Oct 31, 2018 at 10:19 PM Dave Hansen <dave.hansen@xxxxxxxxx> wrote: > On 10/31/18 1:19 AM, owner-linux-mm@xxxxxxxxx wrote: > > -These are currently used in two places in the kernel: > > +These are currently used in three places in the kernel: > > > > (1) By ramfs to mark the address spaces of its inodes when they are created, > > and this mark remains for the life of the inode. > > @@ -154,6 +154,8 @@ These are currently used in two places in the kernel: > > swapped out; the application must touch the pages manually if it wants to > > ensure they're in memory. > > > > + (3) By the i915 driver to mark pinned address space until it's unpinned. > > mlock() and ramfs usage are pretty easy to track down. /proc/$pid/smaps > or /proc/meminfo can show us mlock() and good ol' 'df' and friends can > show us ramfs the extent of pinned memory. > > With these, if we see "Unevictable" in meminfo bump up, we at least have > a starting point to find the cause. > > Do we have an equivalent for i915? AFAIK, there is no way to get i915 unevictable page count, some modification to i915 debugfs is required. _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
