Re: [PATCH 0/4] arch: Introduce smp_load_acquire() and smp_store_release()
On Wed, Dec 18, 2013 at 08:08:06PM +0100, Peter Zijlstra wrote:
>
> This should hopefully be the last posting of this series -- people felt it
> needed one more mostly because last time I typoed the linux-kernel email
> address.
>
> If there are no further comments, Ingo will merge these patches in the next
> few
> days.
They still look good to me!
Thanx, Paul
> ---
>
> These patches introduce 2 new barrier primitives:
>
> smp_load_acquire(p)
> smp_store_release(p, v)
>
> See the first patch, which changes Documentation/memory-barriers.txt, to find
> the exact definitions of what an ACQUIRE/RELEASE barrier is -- previously
> known
> as LOCK/UNLOCK barriers.
>
> The second patch moves the smp_mb__{before,after}_atomic_{dec,inc}() barriers
> to asm/atomic.h for arc and hexagon -- they were already there for all other
> archs.
>
> This cleans up asm/barrier.h, and the third patch makes more agressive use of
> asm-generic/barrier.h to implement the simple cases.
>
> Then the fourth patch adds the new primitives.
>
> Previous versions were widely build tested -- this version is not, but it also
> not significantly different.
>
> These patches apply to:
>
> tip/master
>
>
> ---
> Changes since the last version --
> lkml.kernel.org/r/20131213145657.265414...@infradead.org
>
> - fixed linux-kernel email address
> - updated the Documentation patch
>
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/4] arch: Introduce smp_load_acquire() and smp_store_release()
This should hopefully be the last posting of this series -- people felt it
needed one more mostly because last time I typoed the linux-kernel email
address.
If there are no further comments, Ingo will merge these patches in the next few
days.
---
These patches introduce 2 new barrier primitives:
smp_load_acquire(p)
smp_store_release(p, v)
See the first patch, which changes Documentation/memory-barriers.txt, to find
the exact definitions of what an ACQUIRE/RELEASE barrier is -- previously known
as LOCK/UNLOCK barriers.
The second patch moves the smp_mb__{before,after}_atomic_{dec,inc}() barriers
to asm/atomic.h for arc and hexagon -- they were already there for all other
archs.
This cleans up asm/barrier.h, and the third patch makes more agressive use of
asm-generic/barrier.h to implement the simple cases.
Then the fourth patch adds the new primitives.
Previous versions were widely build tested -- this version is not, but it also
not significantly different.
These patches apply to:
tip/master
---
Changes since the last version --
lkml.kernel.org/r/20131213145657.265414...@infradead.org
- fixed linux-kernel email address
- updated the Documentation patch
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/4] arch: Introduce smp_load_acquire() and smp_store_release()
This should hopefully be the last posting of this series -- people felt it
needed one more mostly because last time I typoed the linux-kernel email
address.
If there are no further comments, Ingo will merge these patches in the next few
days.
---
These patches introduce 2 new barrier primitives:
smp_load_acquire(p)
smp_store_release(p, v)
See the first patch, which changes Documentation/memory-barriers.txt, to find
the exact definitions of what an ACQUIRE/RELEASE barrier is -- previously known
as LOCK/UNLOCK barriers.
The second patch moves the smp_mb__{before,after}_atomic_{dec,inc}() barriers
to asm/atomic.h for arc and hexagon -- they were already there for all other
archs.
This cleans up asm/barrier.h, and the third patch makes more agressive use of
asm-generic/barrier.h to implement the simple cases.
Then the fourth patch adds the new primitives.
Previous versions were widely build tested -- this version is not, but it also
not significantly different.
These patches apply to:
tip/master
---
Changes since the last version --
lkml.kernel.org/r/20131213145657.265414...@infradead.org
- fixed linux-kernel email address
- updated the Documentation patch
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/4] arch: Introduce smp_load_acquire() and smp_store_release()
On Wed, Dec 18, 2013 at 08:08:06PM +0100, Peter Zijlstra wrote:
This should hopefully be the last posting of this series -- people felt it
needed one more mostly because last time I typoed the linux-kernel email
address.
If there are no further comments, Ingo will merge these patches in the next
few
days.
They still look good to me!
Thanx, Paul
---
These patches introduce 2 new barrier primitives:
smp_load_acquire(p)
smp_store_release(p, v)
See the first patch, which changes Documentation/memory-barriers.txt, to find
the exact definitions of what an ACQUIRE/RELEASE barrier is -- previously
known
as LOCK/UNLOCK barriers.
The second patch moves the smp_mb__{before,after}_atomic_{dec,inc}() barriers
to asm/atomic.h for arc and hexagon -- they were already there for all other
archs.
This cleans up asm/barrier.h, and the third patch makes more agressive use of
asm-generic/barrier.h to implement the simple cases.
Then the fourth patch adds the new primitives.
Previous versions were widely build tested -- this version is not, but it also
not significantly different.
These patches apply to:
tip/master
---
Changes since the last version --
lkml.kernel.org/r/20131213145657.265414...@infradead.org
- fixed linux-kernel email address
- updated the Documentation patch
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
