diff options
author | David S. Miller <davem@davemloft.net> | 2018-03-23 11:24:57 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-03-23 11:31:58 -0400 |
commit | 03fe2debbb2771fb90881e4ce8109b09cf772a5c (patch) | |
tree | fbaf8738296b2e9dcba81c6daef2d515b6c4948c /mm/vmscan.c | |
parent | 6686c459e1449a3ee5f3fd313b0a559ace7a700e (diff) | |
parent | f36b7534b83357cf52e747905de6d65b4f7c2512 (diff) |
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
Fun set of conflict resolutions here...
For the mac80211 stuff, these were fortunately just parallel
adds. Trivially resolved.
In drivers/net/phy/phy.c we had a bug fix in 'net' that moved the
function phy_disable_interrupts() earlier in the file, whilst in
'net-next' the phy_error() call from this function was removed.
In net/ipv4/xfrm4_policy.c, David Ahern's changes to remove the
'rt_table_id' member of rtable collided with a bug fix in 'net' that
added a new struct member "rt_mtu_locked" which needs to be copied
over here.
The mlxsw driver conflict consisted of net-next separating
the span code and definitions into separate files, whilst
a 'net' bug fix made some changes to that moved code.
The mlx5 infiniband conflict resolution was quite non-trivial,
the RDMA tree's merge commit was used as a guide here, and
here are their notes:
====================
Due to bug fixes found by the syzkaller bot and taken into the for-rc
branch after development for the 4.17 merge window had already started
being taken into the for-next branch, there were fairly non-trivial
merge issues that would need to be resolved between the for-rc branch
and the for-next branch. This merge resolves those conflicts and
provides a unified base upon which ongoing development for 4.17 can
be based.
Conflicts:
drivers/infiniband/hw/mlx5/main.c - Commit 42cea83f9524
(IB/mlx5: Fix cleanup order on unload) added to for-rc and
commit b5ca15ad7e61 (IB/mlx5: Add proper representors support)
add as part of the devel cycle both needed to modify the
init/de-init functions used by mlx5. To support the new
representors, the new functions added by the cleanup patch
needed to be made non-static, and the init/de-init list
added by the representors patch needed to be modified to
match the init/de-init list changes made by the cleanup
patch.
Updates:
drivers/infiniband/hw/mlx5/mlx5_ib.h - Update function
prototypes added by representors patch to reflect new function
names as changed by cleanup patch
drivers/infiniband/hw/mlx5/ib_rep.c - Update init/de-init
stage list to match new order from cleanup patch
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'mm/vmscan.c')
-rw-r--r-- | mm/vmscan.c | 31 |
1 files changed, 16 insertions, 15 deletions
diff --git a/mm/vmscan.c b/mm/vmscan.c index bee53495a829..cd5dc3faaa57 100644 --- a/mm/vmscan.c +++ b/mm/vmscan.c | |||
@@ -1780,6 +1780,20 @@ shrink_inactive_list(unsigned long nr_to_scan, struct lruvec *lruvec, | |||
1780 | set_bit(PGDAT_WRITEBACK, &pgdat->flags); | 1780 | set_bit(PGDAT_WRITEBACK, &pgdat->flags); |
1781 | 1781 | ||
1782 | /* | 1782 | /* |
1783 | * If dirty pages are scanned that are not queued for IO, it | ||
1784 | * implies that flushers are not doing their job. This can | ||
1785 | * happen when memory pressure pushes dirty pages to the end of | ||
1786 | * the LRU before the dirty limits are breached and the dirty | ||
1787 | * data has expired. It can also happen when the proportion of | ||
1788 | * dirty pages grows not through writes but through memory | ||
1789 | * pressure reclaiming all the clean cache. And in some cases, | ||
1790 | * the flushers simply cannot keep up with the allocation | ||
1791 | * rate. Nudge the flusher threads in case they are asleep. | ||
1792 | */ | ||
1793 | if (stat.nr_unqueued_dirty == nr_taken) | ||
1794 | wakeup_flusher_threads(WB_REASON_VMSCAN); | ||
1795 | |||
1796 | /* | ||
1783 | * Legacy memcg will stall in page writeback so avoid forcibly | 1797 | * Legacy memcg will stall in page writeback so avoid forcibly |
1784 | * stalling here. | 1798 | * stalling here. |
1785 | */ | 1799 | */ |
@@ -1791,22 +1805,9 @@ shrink_inactive_list(unsigned long nr_to_scan, struct lruvec *lruvec, | |||
1791 | if (stat.nr_dirty && stat.nr_dirty == stat.nr_congested) | 1805 | if (stat.nr_dirty && stat.nr_dirty == stat.nr_congested) |
1792 | set_bit(PGDAT_CONGESTED, &pgdat->flags); | 1806 | set_bit(PGDAT_CONGESTED, &pgdat->flags); |
1793 | 1807 | ||
1794 | /* | 1808 | /* Allow kswapd to start writing pages during reclaim. */ |
1795 | * If dirty pages are scanned that are not queued for IO, it | 1809 | if (stat.nr_unqueued_dirty == nr_taken) |
1796 | * implies that flushers are not doing their job. This can | ||
1797 | * happen when memory pressure pushes dirty pages to the end of | ||
1798 | * the LRU before the dirty limits are breached and the dirty | ||
1799 | * data has expired. It can also happen when the proportion of | ||
1800 | * dirty pages grows not through writes but through memory | ||
1801 | * pressure reclaiming all the clean cache. And in some cases, | ||
1802 | * the flushers simply cannot keep up with the allocation | ||
1803 | * rate. Nudge the flusher threads in case they are asleep, but | ||
1804 | * also allow kswapd to start writing pages during reclaim. | ||
1805 | */ | ||
1806 | if (stat.nr_unqueued_dirty == nr_taken) { | ||
1807 | wakeup_flusher_threads(WB_REASON_VMSCAN); | ||
1808 | set_bit(PGDAT_DIRTY, &pgdat->flags); | 1810 | set_bit(PGDAT_DIRTY, &pgdat->flags); |
1809 | } | ||
1810 | 1811 | ||
1811 | /* | 1812 | /* |
1812 | * If kswapd scans pages marked marked for immediate | 1813 | * If kswapd scans pages marked marked for immediate |