Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 30 Jul 2001 14:50:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 30 Jul 2001 14:50:34 -0400 Received: from nat-pool-meridian.redhat.com ([199.183.24.200]:27830 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Mon, 30 Jul 2001 14:50:27 -0400 Date: Mon, 30 Jul 2001 14:50:21 -0400 (EDT) From: Ingo Molnar X-X-Sender: To: cc: Linus Torvalds , , , , Subject: Re: [PATCH] [IMPORTANT] Re: 2.4.7 softirq incorrectness. In-Reply-To: <200107291752.VAA19495@ms2.inr.ac.ru> 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 Original-Recipient: rfc822;linux-kernel-outgoing > > I think the latency issue was really the fact that we weren't always > > running softirqs in a timely fashion after they had been disabled by a > > "disable_bh()". That is fixed with the new softirq stuff, regardless of > > the other issues. nope. i observed latency issues with restart + ksoftirqd as well. [when i first saw these latency problems i basically had ksoftirqd implemented independently from your patch, and threw the idea away because it was insufficient from the latency point of view.] Those latencies are harder to observe because they are not 1/HZ anymore but several hundred millisecs at most. Plus, like i said previously, pushing IRQ context work into a scheduler-level context 'feels' incorrect to me - it only makes the latencies less visible. I'll do some measurements. Ingo - 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/