From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753892AbZBRNsS (ORCPT ); Wed, 18 Feb 2009 08:48:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752183AbZBRNr7 (ORCPT ); Wed, 18 Feb 2009 08:47:59 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:44316 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752015AbZBRNr6 (ORCPT ); Wed, 18 Feb 2009 08:47:58 -0500 Date: Wed, 18 Feb 2009 14:47:38 +0100 From: Ingo Molnar To: Patrick McHardy Cc: Oleg Nesterov , Peter Zijlstra , Stephen Hemminger , David Miller , Rick Jones , Eric Dumazet , netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, tglx@linutronix.de, Martin Josefsson , linux-kernel@vger.kernel.org Subject: Re: [patch] timers: add mod_timer_pending() Message-ID: <20090218134738.GD1300@elte.hu> References: <20090218051906.174295181@vyatta.com> <20090218052747.437271195@vyatta.com> <20090218092041.GC3294@elte.hu> <499BDDFE.5010101@trash.net> <20090218120508.GB4100@elte.hu> <499C000A.4040205@trash.net> <20090218125049.GA28791@elte.hu> <499C0519.2050204@trash.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <499C0519.2050204@trash.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Patrick McHardy wrote: > Ingo Molnar wrote: >> To accelerate matters i've committed the new API patch into a new >> standalone topic branch: tip:timers/new-apis. >> >> Unless there are objections or test failures, you (or Stephen or >> David) can then git-pull it into the networking tree via the Git >> coordinates below - and you'll get this single commit in a surgical >> manner - no other timer changes are included. >> >> Doing so has the advantage of: >> >> - You not having to wait a kernel cycle for the API to go >> upstream. >> >> - You can also push it upstream without waiting for the timer tree. >> (the timer tree and the networking tree will share the exact same >> commit) >> >> - It will also all merge cleanly with the timer tree in linux-next, >> etc. >> >> I'd suggest to do it in about a week, to make sure any after effects >> have trickled down and to make sure the topic has become append-only. >> You can ping Thomas and me about testing/review status then, whenever >> you want to do the pull. > > Thanks Ingo. I'll wait for Stephen to rebase his patches on > top of your change and the test results and will let you know. Stress-testing here in the last ~2 hours on eight x86 test-boxes showed no problems so far. Ingo