Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751521AbdISTxP (ORCPT ); Tue, 19 Sep 2017 15:53:15 -0400 Received: from mail-pg0-f54.google.com ([74.125.83.54]:44537 "EHLO mail-pg0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751097AbdISTxN (ORCPT ); Tue, 19 Sep 2017 15:53:13 -0400 X-Google-Smtp-Source: AOwi7QCSrZ/2pjVBW2q6QZ4vQBbCh8gglebq1lnhEi8PQLQR6SHLFR1s0TPQsG1eRRo/C+x1lkK9zg== From: Jens Axboe To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org Cc: hannes@cmpxchg.org, clm@fb.com, jack@suse.cz Subject: [PATCH 0/6] More graceful flusher thread memory reclaim wakeup Date: Tue, 19 Sep 2017 13:53:01 -0600 Message-Id: <1505850787-18311-1-git-send-email-axboe@kernel.dk> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 642 Lines: 15 We've had some issues with writeback in presence of memory reclaim at Facebook, and this patch set attempts to fix it up. The real functional change is the last patch in the series, the first 5 are prep and cleanup patches. The basic idea is that we have callers that call wakeup_flusher_threads() with nr_pages == 0. This means 'writeback everything'. For memory reclaim situations, we can end up queuing a TON of these kinds of writeback units. This can cause softlockups and further memory issues, since we allocate huge amounts of struct wb_writeback_work to handle this writeback. Handle this situation more gracefully. -- Jens Axboe