Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757150AbZLOApi (ORCPT ); Mon, 14 Dec 2009 19:45:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754065AbZLOApg (ORCPT ); Mon, 14 Dec 2009 19:45:36 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:50601 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753808AbZLOApg (ORCPT ); Mon, 14 Dec 2009 19:45:36 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 From: KOSAKI Motohiro To: Rik van Riel Subject: Re: [PATCH 4/8] Use prepare_to_wait_exclusive() instead prepare_to_wait() Cc: kosaki.motohiro@jp.fujitsu.com, lwoodman@redhat.com, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, minchan.kim@gmail.com In-Reply-To: <4B264CCA.5010609@redhat.com> References: <20091214212936.BBBA.A69D9226@jp.fujitsu.com> <4B264CCA.5010609@redhat.com> Message-Id: <20091215085631.CDAD.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.50.07 [ja] Date: Tue, 15 Dec 2009 09:45:27 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2199 Lines: 67 > On 12/14/2009 07:30 AM, KOSAKI Motohiro wrote: > > if we don't use exclusive queue, wake_up() function wake _all_ waited > > task. This is simply cpu wasting. > > > > Signed-off-by: KOSAKI Motohiro > > > if (zone_watermark_ok(zone, sc->order, low_wmark_pages(zone), > > 0, 0)) { > > - wake_up(wq); > > + wake_up_all(wq); > > finish_wait(wq,&wait); > > sc->nr_reclaimed += sc->nr_to_reclaim; > > return -ERESTARTSYS; > > I believe we want to wake the processes up one at a time > here. If the queue of waiting processes is very large > and the amount of excess free memory is fairly low, the > first processes that wake up can take the amount of free > memory back down below the threshold. The rest of the > waiters should stay asleep when this happens. OK. Actually, wake_up() and wake_up_all() aren't different so much. Although we use wake_up(), the task wake up next task before try to alloate memory. then, it's similar to wake_up_all(). However, there are few difference. recent scheduler latency improvement effort reduce default scheduler latency target. it mean, if we have lots tasks of running state, the task have very few time slice. too frequently context switch decrease VM efficiency. Thank you, Rik. I didn't notice wake_up() makes better performance than wake_up_all() on current kernel. Subject: [PATCH 9/8] replace wake_up_all with wake_up Fix typo. Signed-off-by: KOSAKI Motohiro --- mm/vmscan.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/mm/vmscan.c b/mm/vmscan.c index e5adb7a..b3b4e77 100644 --- a/mm/vmscan.c +++ b/mm/vmscan.c @@ -1644,7 +1644,7 @@ static int shrink_zone_begin(struct zone *zone, struct scan_control *sc) return 0; found_lots_memory: - wake_up_all(wq); + wake_up(wq); stop_reclaim: finish_wait(wq, &wait); sc->nr_reclaimed += sc->nr_to_reclaim; -- 1.6.5.2 -- 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/