Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Mar 2003 17:39:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Mar 2003 17:39:06 -0500 Received: from packet.digeo.com ([12.110.80.53]:17550 "EHLO packet.digeo.com") by vger.kernel.org with ESMTP id ; Tue, 11 Mar 2003 17:39:05 -0500 Date: Tue, 11 Mar 2003 14:44:48 -0800 From: Andrew Morton To: george anzinger Cc: torvalds@transmeta.com, felipe_alfaro@linuxmail.org, cobra@compuserve.com, linux-kernel@vger.kernel.org Subject: Re: Runaway cron task on 2.5.63/4 bk? Message-Id: <20030311144448.4d9ee416.akpm@digeo.com> In-Reply-To: <3E6DB852.5060603@mvista.com> References: <3E6DB852.5060603@mvista.com> X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Mar 2003 22:49:41.0695 (UTC) FILETIME=[80C77CF0:01C2E820] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 966 Lines: 21 george anzinger wrote: > > Ok, here is what I have. I changed nano sleep to use a local 64-bit > value for the target expire time in jiffies. As much as MAX-INT/2-1 > will be put in the timer at any one time. It loops till the target > time is met or exceeded. The changes affect (clock)nanosleep only and > not timers (they still error out for large values). > > Issues: The conversion of timespec to jiffies_64 is most easily done > by the asm mpy instruction, which results in the required 64 bit > result, but C doesn't want to do this sort of thing. gcc will generate 64bit * 64bit multiplies without resorting to any library code and you can probably do the division with do_div(). - 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/