From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267358AbUHPCmD (ORCPT ); Sun, 15 Aug 2004 22:42:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267367AbUHPCmD (ORCPT ); Sun, 15 Aug 2004 22:42:03 -0400 Received: from mx1.elte.hu ([157.181.1.137]:19944 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S267358AbUHPClu (ORCPT ); Sun, 15 Aug 2004 22:41:50 -0400 Date: Mon, 16 Aug 2004 04:43:14 +0200 From: Ingo Molnar To: Lee Revell Cc: Florian Schmidt , linux-kernel , Felipe Alfaro Solana Subject: Re: [patch] voluntary-preempt-2.6.8.1-P0 Message-ID: <20040816024314.GA8960@elte.hu> References: <20040809104649.GA13299@elte.hu> <20040810132654.GA28915@elte.hu> <20040812235116.GA27838@elte.hu> <1092382825.3450.19.camel@mindpipe> <20040813104817.GI8135@elte.hu> <1092432929.3450.78.camel@mindpipe> <20040814072009.GA6535@elte.hu> <20040815115649.GA26259@elte.hu> <20040816022554.16c3c84a@mango.fruits.de> <1092622121.867.109.camel@krustophenia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1092622121.867.109.camel@krustophenia.net> User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-4.9, required 5.9, autolearn=not spam, BAYES_00 -4.90 X-ELTE-SpamLevel: X-ELTE-SpamScore: -4 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Lee Revell wrote: > http://krustophenia.net/testresults.php?dataset=2.6.8.1-P0 nice. (What is the difference between the left-hand and the right-hand graphs - why is the right-hand side one 'wider'?) > The peaks on this graph should correspond directly to the length of > the non-preemptible critical section reported by Ingo's latency > tracer. I think the large peak around 580-600usecs is caused by the > extract_entropy issue (which can be hit by regular processes and > ksoftirqd), and the large peak around 80-100 by the XFree86 unmap_vmas > issue, as the times match and these are by far the most common > reported in latency_trace. just to check this theory, could you make __check_and_rekey() an empty function? This should still produce a working random driver, albeit at much reduced entropy. If these latencies have a relationship to the mlockall() issue then this change should have an effect. Ingo