"David S. Miller" wrote:
>
> From: george anzinger <george@xxxxxxxxxx>
> Date: Mon, 20 May 2002 23:08:38 -0700
>
> Nivedita Singhvi wrote:
> >
> > On Mon, 20 May 2002, David S. Miller wrote:
> >
> > > Such rule does not even make this piece of code legal. Consider:
> > >
> > > task1:cpu0: x = counters[smp_processor_id()];
> > > cpu0: PREEMPT
> > > task2:cpu0: x = counters[smp_processor_id()];
> > > task2:cpu0: counters[smp_processor_id()] = x + 1;
> > > cpu0: PREEMPT
> > > task1:cpu0: counters[smp_processor_id()] = x + 1;
> > > full garbage
>
> May be someone could tell me if these matter. If you are
> bumping a counter and you switch cpus in the middle, a.)
> does it matter? and b.) if so which cpu should get the
> count? I sort of thought that, if this were going on, it
> did not really matter as long as some counter was bumped.
>
> That's not the problem. We use per-cpu values for each counter (and
> when the user asks for the value, we add together the values from
> each processor).
>
> Please review the example I quote above, you aren't reading it
> carefully enough.
>
> Let us imagine that we are dealing with counter "X", and
> that the values at the beginning of the example are:
>
> X[0] = 5
> X[1] = 7
> X[2] = ...
>
> Actually, no values matter for the purposes of this example
> except the one for cpu 0. Here is what happens, watch carefully:
>
> > > task1:cpu0: x = counters[smp_processor_id()];
> > > cpu0: PREEMPT
>
> task1 sees 'x' as '5'
>
> > > task2:cpu0: x = counters[smp_processor_id()];
> > > task2:cpu0: counters[smp_processor_id()] = x + 1;
> > > cpu0: PREEMPT
>
> task2 bumps the counter to '6'
>
> > > task1:cpu0: counters[smp_processor_id()] = x + 1;
> > > full garbage
>
> task1 also bumps the counter to '6'
>
> This is the problem. We make these counters non-atomic on purpose
> for performance reasons, so do not mention that as a possible fix.
I understand the issue. The question is what is the
result. Bogus numbers do.. what? Does the kernel crash or
does the user think strange things while every thing just
keeps on working?
As for the fix, I would think that would be more up to the
network folks than me. Atomic is one option, but you can
also disable preemption. It is really light weight, and may
already be disabled in some of these cases.
--
George Anzinger george@xxxxxxxxxx
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
|