From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263212AbTDVPnK (ORCPT ); Tue, 22 Apr 2003 11:43:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263214AbTDVPnK (ORCPT ); Tue, 22 Apr 2003 11:43:10 -0400 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:41447 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id S263212AbTDVPnJ (ORCPT ); Tue, 22 Apr 2003 11:43:09 -0400 Date: Tue, 22 Apr 2003 11:55:00 -0400 (EDT) From: Ingo Molnar X-X-Sender: mingo@devserv.devel.redhat.com To: William Lee Irwin III cc: "Martin J. Bligh" , Andrew Morton , Andrea Arcangeli , , , , Linus Torvalds , , Subject: Re: objrmap and vmtruncate In-Reply-To: <20030422154248.GI8978@holomorphy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 22 Apr 2003, William Lee Irwin III wrote: > I have to apologize for my misstatements of the problem here. You > yourself pointed out to me the hold time was, in fact, linear. Despite > the linearity of the algorithm, the failure mode persists. I've > postponed further investigation until later, when more invasive > techniques are admissible; /proc/ alone will not suffice if linear > algorithms under tasklist_lock can trigger this failure mode. well, i have myself reproduced 30+ secs worth of pid-alloc related lockups on my box, so it's was definitely not a fata morgana, and the pid-allocation code was definitely quadratic near the PID-space saturation point. There might be something else still biting your system, i'd really be interested in hearing more about it. What workload are you using to trigger it? Ingo