On Tue, Apr 13, 2021 at 8:30 PM Rik van Riel <riel@xxxxxxxxxxx> wrote:
>
> On Wed, 2021-04-14 at 09:14 +1000, Dave Chinner wrote:
> > On Tue, Apr 13, 2021 at 10:13:24AM -0600, Jens Axboe wrote:
> >
> > > The initial posting of this patchset did no better, in fact it did
> > > a bit
> > > worse. Performance dropped to the same levels and kswapd was using
> > > as
> > > much CPU as before, but on top of that we also got excessive
> > > swapping.
> > > Not at a high rate, but 5-10MB/sec continually.
> > >
> > > I had some back and forths with Yu Zhao and tested a few new
> > > revisions,
> > > and the current series does much better in this regard. Performance
> > > still dips a bit when page cache fills, but not nearly as much, and
> > > kswapd is using less CPU than before.
> >
> > Profiles would be interesting, because it sounds to me like reclaim
> > *might* be batching page cache removal better (e.g. fewer, larger
> > batches) and so spending less time contending on the mapping tree
> > lock...
> >
> > IOWs, I suspect this result might actually be a result of less lock
> > contention due to a change in batch processing characteristics of
> > the new algorithm rather than it being a "better" algorithm...
>
> That seems quite likely to me, given the issues we have
> had with virtual scan reclaim algorithms in the past.
>
> On Wed, 2021-04-14 at 09:14 +1000, Dave Chinner wrote:
> > On Tue, Apr 13, 2021 at 10:13:24AM -0600, Jens Axboe wrote:
> >
> > > The initial posting of this patchset did no better, in fact it did
> > > a bit
> > > worse. Performance dropped to the same levels and kswapd was using
> > > as
> > > much CPU as before, but on top of that we also got excessive
> > > swapping.
> > > Not at a high rate, but 5-10MB/sec continually.
> > >
> > > I had some back and forths with Yu Zhao and tested a few new
> > > revisions,
> > > and the current series does much better in this regard. Performance
> > > still dips a bit when page cache fills, but not nearly as much, and
> > > kswapd is using less CPU than before.
> >
> > Profiles would be interesting, because it sounds to me like reclaim
> > *might* be batching page cache removal better (e.g. fewer, larger
> > batches) and so spending less time contending on the mapping tree
> > lock...
> >
> > IOWs, I suspect this result might actually be a result of less lock
> > contention due to a change in batch processing characteristics of
> > the new algorithm rather than it being a "better" algorithm...
>
> That seems quite likely to me, given the issues we have
> had with virtual scan reclaim algorithms in the past.
Hi Rik,
Let paste the code so we can move beyond the "batching" hypothesis:
static int __remove_mapping(struct address_space *mapping, struct page *page,
bool reclaimed, struct mem_cgroup *target_memcg)
{
unsigned long flags;
int refcount;
void *shadow = NULL;
BUG_ON(!PageLocked(page));
BUG_ON(mapping != page_mapping(page));
xa_lock_irqsave(&mapping->i_pages, flags);
> SeongJae, what is this algorithm supposed to do when faced
> with situations like this:
I'll assume the questions were directed at me, not SeongJae.
> 1) Running on a system with 8 NUMA nodes, and
> memory
> pressure in one of those nodes.
> 2) Running PostgresQL or Oracle, with hundreds of
> processes mapping the same (very large) shared
> memory segment.
>
> How do you keep your algorithm from falling into the worst
> case virtual scanning scenarios that were crippling the
> 2.4 kernel 15+ years ago on systems with just a few GB of
> memory?
There is a fundamental shift: that time we were scanning for cold pages, and nowadays we are scanning for hot pages.
I'd be surprised if scanning for cold pages didn't fall apart, because it'd find most of the entries accessed, if they are present at all.
Scanning for hot pages, on the other hand, is way better. Let me just reiterate:
1) It will not scan page tables from processes that have been sleeping
since the last scan.
2) It will not scan PTE tables under non-leaf PMD entries that do not
have the accessed bit set, when
CONFIG_HAVE_ARCH_PARENT_PMD_YOUNG=y.
3) It will not zigzag between the PGD table and the same PMD or PTE
table spanning multiple VMAs. In other words, it finishes all the
VMAs with the range of the same PMD or PTE table before it returns
to the PGD table. This optimizes workloads that have large numbers
of tiny VMAs, especially when CONFIG_PGTABLE_LEVELS=5.
So the cost is roughly proportional to the number of referenced pages it discovers. If there is no memory pressure, no scanning at all. For a system under heavy memory pressure, most of the pages are referenced (otherwise why would it be under memory pressure?), and if we use the rmap, we need to scan a lot of pages anyway. Why not just scan them all? This way you save a lot because of batching (now it's time to talk about batching). Besides, page tables have far better memory locality than the rmap. For the shared memory example you gave, the rmap needs to lock *each* page it scans. How many 4KB pages does your large file have? I'll leave the math to you.
Let paste the code so we can move beyond the "batching" hypothesis:
static int __remove_mapping(struct address_space *mapping, struct page *page,
bool reclaimed, struct mem_cgroup *target_memcg)
{
unsigned long flags;
int refcount;
void *shadow = NULL;
BUG_ON(!PageLocked(page));
BUG_ON(mapping != page_mapping(page));
xa_lock_irqsave(&mapping->i_pages, flags);
> SeongJae, what is this algorithm supposed to do when faced
> with situations like this:
I'll assume the questions were directed at me, not SeongJae.
> 1) Running on a system with 8 NUMA nodes, and
> memory
> pressure in one of those nodes.
> 2) Running PostgresQL or Oracle, with hundreds of
> processes mapping the same (very large) shared
> memory segment.
>
> How do you keep your algorithm from falling into the worst
> case virtual scanning scenarios that were crippling the
> 2.4 kernel 15+ years ago on systems with just a few GB of
> memory?
There is a fundamental shift: that time we were scanning for cold pages, and nowadays we are scanning for hot pages.
I'd be surprised if scanning for cold pages didn't fall apart, because it'd find most of the entries accessed, if they are present at all.
Scanning for hot pages, on the other hand, is way better. Let me just reiterate:
1) It will not scan page tables from processes that have been sleeping
since the last scan.
2) It will not scan PTE tables under non-leaf PMD entries that do not
have the accessed bit set, when
CONFIG_HAVE_ARCH_PARENT_PMD_YOUNG=y.
3) It will not zigzag between the PGD table and the same PMD or PTE
table spanning multiple VMAs. In other words, it finishes all the
VMAs with the range of the same PMD or PTE table before it returns
to the PGD table. This optimizes workloads that have large numbers
of tiny VMAs, especially when CONFIG_PGTABLE_LEVELS=5.
So the cost is roughly proportional to the number of referenced pages it discovers. If there is no memory pressure, no scanning at all. For a system under heavy memory pressure, most of the pages are referenced (otherwise why would it be under memory pressure?), and if we use the rmap, we need to scan a lot of pages anyway. Why not just scan them all? This way you save a lot because of batching (now it's time to talk about batching). Besides, page tables have far better memory locality than the rmap. For the shared memory example you gave, the rmap needs to lock *each* page it scans. How many 4KB pages does your large file have? I'll leave the math to you.
Here are some profiles:
zram with the rmap (mainline)
31.03% page_vma_mapped_walk
25.59% lzo1x_1_do_compress
4.63% do_raw_spin_lock
3.89% vma_interval_tree_iter_next
3.33% vma_interval_tree_subtree_search
25.59% lzo1x_1_do_compress
4.63% do_raw_spin_lock
3.89% vma_interval_tree_iter_next
3.33% vma_interval_tree_subtree_search
zram with page table scanning (this patchset)
49.36% lzo1x_1_do_compress
4.54% page_vma_mapped_walk
4.45% memset_erms
3.47% walk_pte_range
2.88% zram_bvec_rw
4.54% page_vma_mapped_walk
4.45% memset_erms
3.47% walk_pte_range
2.88% zram_bvec_rw
Note that these are not just what I saw from some local benchmarks. We have observed *millions* of machines in our fleet.
I encourage you to try it and see for yourself. It's as simple as:
git fetch https://linux-mm.googlesource.com/page-reclaim refs/changes/73/1173/1
CONFIG_LRU_GEN=y
CONFIG_LRU_GEN_ENABLED=y
CONFIG_LRU_GEN=y
CONFIG_LRU_GEN_ENABLED=y
and build and run your favorite benchmarks.
