From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 18 Mar 2016 14:11:36 +0100 From: Jan Kara To: Tejun Heo Cc: Michal Hocko , Tetsuo Handa , viro@zeniv.linux.org.uk, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, Jan Kara Subject: Re: [PATCH] mm,writeback: Don't use memory reserves for wb_start_writeback Message-ID: <20160318131136.GE7152@quack.suse.cz> References: <1457847155-19394-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp> <201603132322.BEA57780.QMVOHFOSFJLOtF@I-love.SAKURA.ne.jp> <20160314160900.GC11400@dhcp22.suse.cz> <20160316204617.GH21104@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160316204617.GH21104@mtj.duckdns.org> Sender: owner-linux-mm@kvack.org List-ID: On Wed 16-03-16 13:46:17, Tejun Heo wrote: > Hello, > > (cc'ing Jan) > > On Mon, Mar 14, 2016 at 05:09:00PM +0100, Michal Hocko wrote: > > On Sun 13-03-16 23:22:23, Tetsuo Handa wrote: > > [...] > > > > I am not familiar with the writeback code so I might be missing > > something essential here but why are we even queueing more and more > > work without checking there has been enough already scheduled or in > > progress. > > > > Something as simple as: > > diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c > > index 6915c950e6e8..aa52e23ac280 100644 > > --- a/fs/fs-writeback.c > > +++ b/fs/fs-writeback.c > > @@ -887,7 +887,7 @@ void wb_start_writeback(struct bdi_writeback *wb, long nr_pages, > > { > > struct wb_writeback_work *work; > > > > - if (!wb_has_dirty_io(wb)) > > + if (!wb_has_dirty_io(wb) || writeback_in_progress(wb)) > > return; > > I'm not sure this would be safe. It shouldn't harm correctness as > wb_start_writeback() isn't used in sync case but this might change > flush behavior in various ways. Dropping GFP_ATOMIC as suggested by > Tetsuo is likely better. Yes, there can be different requests for different numbers of pages to be written and you don't want to discard a request to clean 4000 pages just because a writeback of 10 pages is just running. As Tejun says, this is not a hard requirement but in general it would be unexpected for the users of the api... Honza -- Jan Kara SUSE Labs, CR -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org