From mboxrd@z Thu Jan 1 00:00:00 1970 From: KOSAKI Motohiro Subject: Re: Why PAGEOUT_IO_SYNC stalls for a long time Date: Sun, 1 Aug 2010 17:47:08 +0900 (JST) Message-ID: <20100801174229.4B08.A69D9226@jp.fujitsu.com> References: <20100730115222.4AD8.A69D9226@jp.fujitsu.com> <20100730103018.GE3571@csn.ul.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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 To: Mel Gorman Return-path: In-Reply-To: <20100730103018.GE3571@csn.ul.ie> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > > 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?