From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: shemminger@vyatta.com, kaber@trash.net, rick.jones2@hp.com,
dada1@cosmosbay.com, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, tglx@linutronix.de,
gandalf@wlug.westbo.se, linux-kernel@vger.kernel.org
Subject: Re: [RFT 2/4] Add mod_timer_noact
Date: Wed, 18 Feb 2009 13:39:59 -0800 (PST) [thread overview]
Message-ID: <20090218.133959.193699273.davem@davemloft.net> (raw)
In-Reply-To: <20090218110144.GA4100@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Wed, 18 Feb 2009 12:01:44 +0100
> * David Miller <davem@davemloft.net> wrote:
>
> | Introduce mod_timer_noact() which for example is to replace
> | the calls to del_timer()/add_timer() in
> | __nf_ct_refresh_acct(). It works like mod_timer() but doesn't
> | activate or modify the timeout of an inactive timer which is
> | the behaviour we want in order to be able to use timers as a
> | means of synchronization in nf_conntrack.
>
> It does not mention the overhead to the regular timer interfaces
> at all, nor does it explain the reasons for this change
> adequately.
You (conveniently) skipped this part of his commit message, so
I guess this is the part you didn't read very carefully:
A later patch will modify __nf_ct_refresh_acct() to use
mod_timer_noact() which will then save one spin_lock_irqsave()
/ spin_lock_irqrestore() pair per conntrack timer update. This
will also get rid of the race we currently have without adding
more locking in nf_conntrack.
The whole point is to avoid two spin_lock_irqsave() sequences, thus
taking the timer locks twice.
So Ingo, when you say in response:
Why don't you use?
if (del_timer())
add_timer();
you really look foolish and, in fact, disrespectful to Stephen.
This was my objection to your email, it proved that you didn't
really read his changelog message. He explained perfectly well
what the final goal was of his changes.
And you have this knee-jerk reaction quite often.
next prev parent reply other threads:[~2009-02-18 21:50 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 ` 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 [this message]
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
[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=20090218.133959.193699273.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dada1@cosmosbay.com \
--cc=gandalf@wlug.westbo.se \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®