From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Christoph Lameter <cl@linux.com>, Tejun Heo <tj@kernel.org>,
akpm@linuxfoundation.org, Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Steven Rostedt <srostedt@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [raw v1 2/4] [NET] Use raw_cpu ops for SNMP stats
Date: Tue, 8 Oct 2013 12:26:45 +0200 [thread overview]
Message-ID: <20131008102645.GA22639@gmail.com> (raw)
In-Reply-To: <20131008102142.GT3081@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Oct 08, 2013 at 09:21:14AM +0200, Ingo Molnar wrote:
> >
> > * Christoph Lameter <cl@linux.com> wrote:
> >
> > > SNMP stats are not protected by preemption but by bh handling.
> >
> > Most forms of bh exclusion work via the preemption count though, and
> > softirq contexts themselves are generally not preemptible [to other CPUs]
> > either.
> >
> > So the warnings should, in most cases, not trigger.
>
> Right, so softirqs run either in the irq tail at which point
> preempt_count += SOFTIRQ_OFFSET and thus preemption is disabled, or it
> runs in ksoftirqd which has strict cpu affinity which also disables the
> warning, and it also increments preempt_count with SOFTIRQ_OFFSET to
> exclude the softirq from interrupts while its running, also disabling
> the warning.
A third context would be syscall-level code that runs with
local_bh_disable()/enable() - but that too ought to have the preempt count
elevated.
> So it should very much not trigger.. if it does you want to know about
> it.
Yes. If nothing else then for the education value.
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-08 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131007183226.334180014@linux.com>
2013-10-07 18:31 ` [raw v1 1/4] Use raw_cpu ops for determining current NUMA node Christoph Lameter
2013-10-07 18:31 ` Christoph Lameter
2013-10-07 18:31 ` [raw v1 2/4] [NET] Use raw_cpu ops for SNMP stats Christoph Lameter
2013-10-08 7:21 ` Ingo Molnar
2013-10-08 10:21 ` Peter Zijlstra
2013-10-08 10:26 ` Ingo Molnar [this message]
2013-10-07 18:32 ` [raw v1 4/4] net: __this_cpu_inc in route.c Christoph Lameter
2013-10-07 18:32 ` [raw v1 3/4] Use raw_cpu_write for initialization of per cpu refcount Christoph Lameter
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=20131008102645.GA22639@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.