Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
* [PATCH] appendix/whymb: Fix a typo, smb_wmb into smp_wmb
@ 2017-02-17  1:54 SeongJae Park
  2017-02-19 22:14 ` Paul E. McKenney
  0 siblings, 1 reply; 2+ messages in thread
From: SeongJae Park @ 2017-02-17  1:54 UTC (permalink / raw)
  To: paulmck; +Cc: perfbook, SeongJae Park

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 appendix/whymb/whymemorybarriers.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/appendix/whymb/whymemorybarriers.tex b/appendix/whymb/whymemorybarriers.tex
index 9002047a9878..3a22e46beb0c 100644
--- a/appendix/whymb/whymemorybarriers.tex
+++ b/appendix/whymb/whymemorybarriers.tex
@@ -2265,7 +2265,7 @@ a write to a given MMIO register affects the value that will next be
 read from {\em some other} MMIO register.

 It is not clear why SPARC does not define \co{wmb()} to be
-\co{membar #MemIssue} and \co{smb_wmb()} to be
+\co{membar #MemIssue} and \co{smp_wmb()} to be
 \co{membar #StoreStore},
 as the current definitions seem vulnerable to bugs in some drivers.
 It is quite possible that all the SPARC CPUs that Linux runs on
-- 
2.10.0


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] appendix/whymb: Fix a typo, smb_wmb into smp_wmb
  2017-02-17  1:54 [PATCH] appendix/whymb: Fix a typo, smb_wmb into smp_wmb SeongJae Park
@ 2017-02-19 22:14 ` Paul E. McKenney
  0 siblings, 0 replies; 2+ messages in thread
From: Paul E. McKenney @ 2017-02-19 22:14 UTC (permalink / raw)
  To: SeongJae Park; +Cc: perfbook

On Fri, Feb 17, 2017 at 10:54:15AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good eyes, applied, thank you!

							Thanx, Paul

> ---
>  appendix/whymb/whymemorybarriers.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/appendix/whymb/whymemorybarriers.tex b/appendix/whymb/whymemorybarriers.tex
> index 9002047a9878..3a22e46beb0c 100644
> --- a/appendix/whymb/whymemorybarriers.tex
> +++ b/appendix/whymb/whymemorybarriers.tex
> @@ -2265,7 +2265,7 @@ a write to a given MMIO register affects the value that will next be
>  read from {\em some other} MMIO register.
> 
>  It is not clear why SPARC does not define \co{wmb()} to be
> -\co{membar #MemIssue} and \co{smb_wmb()} to be
> +\co{membar #MemIssue} and \co{smp_wmb()} to be
>  \co{membar #StoreStore},
>  as the current definitions seem vulnerable to bugs in some drivers.
>  It is quite possible that all the SPARC CPUs that Linux runs on
> -- 
> 2.10.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-02-19 22:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-17  1:54 [PATCH] appendix/whymb: Fix a typo, smb_wmb into smp_wmb SeongJae Park
2017-02-19 22:14 ` Paul E. McKenney

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox