From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id 7D14F600429 for ; Sun, 1 Aug 2010 04:47:13 -0400 (EDT) Received: from m1.gw.fujitsu.co.jp ([10.0.50.71]) by fgwmail6.fujitsu.co.jp (Fujitsu Gateway) with ESMTP id o718lAfs032157 for (envelope-from kosaki.motohiro@jp.fujitsu.com); Sun, 1 Aug 2010 17:47:10 +0900 Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 241D345DE52 for ; Sun, 1 Aug 2010 17:47:10 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id ECFF745DE4D for ; Sun, 1 Aug 2010 17:47:09 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id D85F41DB8057 for ; Sun, 1 Aug 2010 17:47:09 +0900 (JST) Received: from m107.s.css.fujitsu.com (m107.s.css.fujitsu.com [10.249.87.107]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 9A8F41DB804F for ; Sun, 1 Aug 2010 17:47:09 +0900 (JST) From: KOSAKI Motohiro Subject: Re: Why PAGEOUT_IO_SYNC stalls for a long time In-Reply-To: <20100730103018.GE3571@csn.ul.ie> References: <20100730115222.4AD8.A69D9226@jp.fujitsu.com> <20100730103018.GE3571@csn.ul.ie> Message-Id: <20100801174229.4B08.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Sun, 1 Aug 2010 17:47:08 +0900 (JST) Sender: owner-linux-mm@kvack.org To: Mel Gorman Cc: kosaki.motohiro@jp.fujitsu.com, Wu Fengguang , Andrew Morton , stable@kernel.org, Rik van Riel , Christoph Hellwig , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "linux-mm@kvack.org" , Dave Chinner , Chris Mason , Nick Piggin , Johannes Weiner , KAMEZAWA Hiroyuki , Andrea Arcangeli , Minchan Kim , Andreas Mohr , Bill Davidsen , Ben Gamari List-ID: > > side note: page lock contention is very common case. > > > > For case (8), I don't think sleeping is right way. get_page() is used in really various place of > > our kernel. so we can't assume it's only temporary reference count increasing. > > In what case is a munlocked pages reference count permanently increased and > why is this not a memory leak? V4L, audio, GEM and/or other multimedia driver? -- 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