From: Ingo Molnar <mingo@elte.hu>
To: Patrick McHardy <kaber@trash.net>
Cc: Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephen Hemminger <shemminger@vyatta.com>,
David Miller <davem@davemloft.net>,
Rick Jones <rick.jones2@hp.com>,
Eric Dumazet <dada1@cosmosbay.com>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
tglx@linutronix.de, Martin Josefsson <gandalf@wlug.westbo.se>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] timers: add mod_timer_pending()
Date: Wed, 18 Feb 2009 14:47:38 +0100 [thread overview]
Message-ID: <20090218134738.GD1300@elte.hu> (raw)
In-Reply-To: <499C0519.2050204@trash.net>
* Patrick McHardy <kaber@trash.net> 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
next prev parent reply other threads:[~2009-02-18 13:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090218051906.174295181@vyatta.com>
[not found] ` <20090218052747.437271195@vyatta.com>
[not found] ` <20090218092041.GC3294@elte.hu>
[not found] ` <20090218.013007.117003889.davem@davemloft.net>
2009-02-18 11:01 ` [RFT 2/4] Add mod_timer_noact Ingo Molnar
2009-02-18 11:39 ` Jarek Poplawski
2009-02-18 12:37 ` Ingo Molnar
2009-02-18 12:33 ` Patrick McHardy
2009-02-18 21:39 ` David Miller
2009-02-18 21:51 ` Ingo Molnar
2009-02-18 22:04 ` David Miller
2009-02-18 22:42 ` Peter Zijlstra
2009-02-18 22:47 ` David Miller
2009-02-18 22:56 ` Stephen Hemminger
[not found] ` <499BDDFE.5010101@trash.net>
2009-02-18 12:05 ` [patch] timers: add mod_timer_pending() Ingo Molnar
[not found] ` <499C000A.4040205@trash.net>
2009-02-18 12:50 ` Ingo Molnar
2009-02-18 12:54 ` Patrick McHardy
2009-02-18 13:47 ` Ingo Molnar [this message]
[not found] ` <20090218052747.321329022@vyatta.com>
[not found] ` <20090219114719.560999b5@extreme>
[not found] ` <499DEF49.3040602@cosmosbay.com>
[not found] ` <49A7F262.8040805@cosmosbay.com>
2009-02-27 16:08 ` [PATCH] rcu: increment quiescent state counter in ksoftirqd() Eric Dumazet
2009-02-27 16:34 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090218134738.GD1300@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=gandalf@wlug.westbo.se \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rick.jones2@hp.com \
--cc=shemminger@vyatta.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox