Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 13 Feb 2002 11:19:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 13 Feb 2002 11:19:45 -0500 Received: from mailout03.sul.t-online.com ([194.25.134.81]:45491 "EHLO mailout03.sul.t-online.com") by vger.kernel.org with ESMTP id ; Wed, 13 Feb 2002 11:19:34 -0500 To: Andrew Morton Cc: linux-kernel@vger.kernel.org Subject: Re: What is a livelock? (was: [patch] sys_sync livelock fix) In-Reply-To: <3C69A18A.501BAD42@zip.com.au> <3C69A18A.501BAD42@zip.com.au> <87y9hyw4b6.fsf@tigram.bogus.local> <3C69C7E9.E01C3532@zip.com.au> <87pu3aw1ue.fsf@tigram.bogus.local> <3C69D1FC.195CD36@zip.com.au> From: Olaf Dietsche Date: Wed, 13 Feb 2002 17:19:00 +0100 Message-ID: <87bsetwe17.fsf@tigram.bogus.local> Lines: 15 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Artificial Intelligence, i386-debian-linux) 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 Andrew Morton writes: > Olaf Dietsche wrote: >> >> I still don't get it :-(. When there is more work, this more work >> needs to be done. So, how could livelock be considered a bug? It's >> just overload. Or is this about the work, which must be done _after_ >> the queue is empty? >> > ... > [good explanation, so even I grasped it :-)] Thanks to all, who tried hard explaining livelock. Regards, Olaf. - 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/