Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755149AbbHFI4F (ORCPT ); Thu, 6 Aug 2015 04:56:05 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:33222 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753704AbbHFIzl (ORCPT ); Thu, 6 Aug 2015 04:55:41 -0400 Message-ID: <1438851337.4626.72.camel@gmail.com> Subject: Re: [PATCH] mm: add resched points to remap_pmd_range/ioremap_pmd_range From: Mike Galbraith To: =?ISO-8859-1?Q?J=F6rn?= Engel Cc: Michal Hocko , Spencer Baugh , Toshi Kani , Andrew Morton , Fengguang Wu , Joern Engel , "Kirill A. Shutemov" , Mel Gorman , Johannes Weiner , Shachar Raindel , Boaz Harrosh , Andy Lutomirski , Joonsoo Kim , Andrey Ryabinin , Roman Pen , Andrey Konovalov , Eric Dumazet , Dmitry Vyukov , Rob Jones , WANG Chao , open list , "open list:MEMORY MANAGEMENT" , Spencer Baugh Date: Thu, 06 Aug 2015 10:55:37 +0200 In-Reply-To: <20150730165803.GA17882@Sligo.logfs.org> References: <1437688476-3399-3-git-send-email-sbaugh@catern.com> <20150724070420.GF4103@dhcp22.suse.cz> <20150724165627.GA3458@Sligo.logfs.org> <20150727070840.GB11317@dhcp22.suse.cz> <20150727151814.GR9641@Sligo.logfs.org> <20150728133254.GI24972@dhcp22.suse.cz> <20150728170844.GY9641@Sligo.logfs.org> <20150729095439.GD15801@dhcp22.suse.cz> <1438269775.23663.58.camel@gmail.com> <20150730165803.GA17882@Sligo.logfs.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1484 Lines: 31 On Thu, 2015-07-30 at 09:58 -0700, Jörn Engel wrote: > On Thu, Jul 30, 2015 at 05:22:55PM +0200, Mike Galbraith wrote: > > > > I piddled about with the thought that it might be nice to be able to > > sprinkle cond_resched() about to cut rt latencies without wrecking > > normal load throughput, cobbled together a cond_resched_rt(). > > > > On my little box that was a waste of time, as the biggest hits are block > > softirq and free_hot_cold_page_list(). > > Block softirq is one of our problems as well. It is a bit of a joke > that __do_softirq() moves work to ksoftirqd after 2ms, but block softirq > can take several 100ms in bad cases. On my little desktop box, one blk_done_softirq() loop iteration can take up to a few milliseconds, leaving me wondering if breaking that loop will help a studly box much. iow, I'd like to know how bad it gets, if one iteration can be huge, loop breaking there is fairly pointless, and I can stop fiddling. Do you happen to know iteration time during a size huge block softirq hit? On my little box, loop break/re-raise and whatnot improves the general case substantially, but doesn't do much at all for worst case.. or rather the next worst case in a list of unknown length ;-) -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/