On 18 Dec 2014 at 21:07, Rogelio M. Serrano Jr. wrote:
> whats the difference between:
>
> atomic_inc(>count);
>
> and
>
> spin_lock_irq(>lock);
> ++port->count;
> spin_unlock_irq(>lock);
in PaX this kind of change brings the ->count accesses
On 18 Dec 2014 at 21:07, Rogelio M. Serrano Jr. wrote:
whats the difference between:
atomic_inc(port-count);
and
spin_lock_irq(port-lock);
++port-count;
spin_unlock_irq(port-lock);
in PaX this kind of change brings the -count accesses under the coverage
of the REFCOUNT feature. if
On Thu, 18 Dec 2014 21:07:46 + Rogelio M. Serrano Jr. wrote:
> whats the difference between:
>
> atomic_inc(>count);
It is intended to atomically increment a variable of a standard size
(int/long). See [1] for more information.
> and
>
> spin_lock_irq(>lock);
> ++port->count;
>
whats the difference between:
atomic_inc(>count);
and
spin_lock_irq(>lock);
++port->count;
spin_unlock_irq(>lock);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
whats the difference between:
atomic_inc(port-count);
and
spin_lock_irq(port-lock);
++port-count;
spin_unlock_irq(port-lock);
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Thu, 18 Dec 2014 21:07:46 + Rogelio M. Serrano Jr. wrote:
whats the difference between:
atomic_inc(port-count);
It is intended to atomically increment a variable of a standard size
(int/long). See [1] for more information.
and
spin_lock_irq(port-lock);
++port-count;
6 matches
Mail list logo