Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753754AbZL3VQG (ORCPT ); Wed, 30 Dec 2009 16:16:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753496AbZL3VQE (ORCPT ); Wed, 30 Dec 2009 16:16:04 -0500 Received: from ey-out-2122.google.com ([74.125.78.27]:17376 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752957AbZL3VQB (ORCPT ); Wed, 30 Dec 2009 16:16:01 -0500 Date: Wed, 30 Dec 2009 22:15:57 +0100 From: Frederic Weisbecker To: Nico Cc: linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: ksoftirqd problem Message-ID: <20091230211555.GD6322@nowhere> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1226 Lines: 35 On Sun, Dec 13, 2009 at 08:05:29PM +0100, Nico wrote: > > Hi, > > I recently switched to kernel 2.6.32 (self configured/compiled) and I've noticed an odd behavior on one of my servers. I run a bittorrent tracker on one of my servers and when using kernel 2.6.32, every now and then ksoftirqd will jump up to 20% of my CPU for almost a minute. The tracker has a total peers amount of ~45000 peers (if it matters) and this behavior seems to only happen under kernel 2.6.32. Switching back to kernel 2.6.31.1 on the server, ksoftirdq does not behave that way. > > Any thoughts? > > PS: please CC me as I'm not subscribed to the list > > Thanks :) Hi, I wonder if this problem still happens in 2.6.33-rc2. A trace of softirqs during the issue would be helpful to determine which softirq is the culprit: mount -t debugfs /debug echo 1 > /debug/tracing/events/irq/softirq_entry/enable # wait a bit echo 0 > /debug/tracing/events/irq/softirq_entry/enable cat trace Thanks. -- 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/