bib: Update the AMD GPU compute URL
PATCH 1/1 bib: Update the AMD GPU compute URL
From: Borislav Petkov <[email protected]>
The old one is 404.
Signed-off-by Borislav Petkov <[email protected]>
--- bib/hw.bib | 11 +++++------ howto/howto.tex | 2 +- owned/owned.tex | 2 +- 3 files changed, 7 insertions(+), 8 deletions(-)
bib/hw.bib +5 -6
@@ -165,15 +165,14 @@ System Programming", number="24593 rev. 3.13", } -@unpublished{AMD2017OpenCL, +@unpublished{AMD2020ROCm, Author="AMD", - Title="{OpenCL\textsuperscript\texttrademark} Zone---Accelerate Your Applications", - year="2017", - month="January", - note="\url{http://developer.amd.com/tools-and-sdks/opencl-zone/}", + Title="Professional Compute Products - GPUOpen", + year="2020", + month="March", + note="\url{https://gpuopen.com/professional-compute/}", } - @manual{ARMv8Litmus2009, title="ARM Barrier Litmus Tests and Cookbook", author="Richard Grisenthwaite",
howto/howto.tex +1 -1
@@ -324,7 +324,7 @@ Fortunately, there are many alternatives available to you: might check out Norm Matloff's ``Programming on Parallel Machines''~\cite{NormMatloff2013ParProcBook}. Of course, the GPU vendors have quite a bit of additional - information~\cite{AMD2017OpenCL,CyrilZeller2011GPGPUbasics,NVidia2017GPGPU,NVidia2017GPGPU-university}. + information~\cite{AMD2020ROCm,CyrilZeller2011GPGPUbasics,NVidia2017GPGPU,NVidia2017GPGPU-university}. \item If you are interested in POSIX Threads, you might take a look at David R.~Butenhof's book~\cite{Butenhof1997pthreads}. In addition,
owned/owned.tex +1 -1
@@ -398,7 +398,7 @@ Examples of data ownership include: well-suited for GPGPUs.\footnote{ But note that a great many other classes of applications have also been ported to - GPGPUs~\cite{NormMatloff2013ParProcBook,AMD2017OpenCL,NVidia2017GPGPU,NVidia2017GPGPU-university}.} + GPGPUs~\cite{NormMatloff2013ParProcBook,AMD2020ROCm,NVidia2017GPGPU,NVidia2017GPGPU-university}.} \item Operating-system kernels adapted for networking, where each connection (also called \emph{flow}~\cite{Shenker89,ZhangPhD,McKenney90}) is assigned to a specific thread.
Signature · 1 line
2.21.0
Paul E. McKenney
AppliedQuoted 5 lines · Borislav Petkov
From: Borislav Petkov <[email protected]>
The old one is 404.
Signed-off-by Borislav Petkov <[email protected]>
Applied, good catch, and thank you!!!
I leave the old entries around due to this bib directory deriving from my main one, so if I rebuild an old paper, I have information telling me what new entry to use. So I took the liberty of modifying your patch as shown below. Please let me know if I messed anything up.
Thanx, Paul
------------------------------------------------------------------------
commit e0424415203223af69bceaa6062e3c91628b2c01
Author: Borislav Petkov <[email protected]> Date: Fri Mar 13 12:08:16 2020 +0100
bib: Update the AMD GPU compute URL
The old one is 404.
Signed-off-by Borislav Petkov <[email protected]>
[ paulmck: Updated to leave old entry as tombstone for other documents. ]
Signed-off-by Paul E. McKenney <[email protected]>
bib/hw.bib +9 -1
@@ -170,7 +170,15 @@ System Programming", Title="{OpenCL\textsuperscript\texttrademark} Zone---Accelerate Your Applications", year="2017", month="January", - note="\url{http://developer.amd.com/tools-and-sdks/opencl-zone/}", + note="\url{http://developer.amd.com/tools-and-sdks/opencl-zone/} (Obsolete, see bibentry AMD2020ROCm)", +} + +@unpublished{AMD2020ROCm, + Author="AMD", + Title="Professional Compute Products - {GPUOpen}", + year="2020", + month="March", + note="\url{https://gpuopen.com/professional-compute/}", }
howto/howto.tex +1 -1
@@ -324,7 +324,7 @@ Fortunately, there are many alternatives available to you: might check out Norm Matloff's ``Programming on Parallel Machines''~\cite{NormMatloff2013ParProcBook}. Of course, the GPU vendors have quite a bit of additional - information~\cite{AMD2017OpenCL,CyrilZeller2011GPGPUbasics,NVidia2017GPGPU,NVidia2017GPGPU-university}. + information~\cite{AMD2020ROCm,CyrilZeller2011GPGPUbasics,NVidia2017GPGPU,NVidia2017GPGPU-university}. \item If you are interested in POSIX Threads, you might take a look at David R.~Butenhof's book~\cite{Butenhof1997pthreads}. In addition,
owned/owned.tex +1 -1
@@ -398,7 +398,7 @@ Examples of data ownership include: well-suited for GPGPUs.\footnote{ But note that a great many other classes of applications have also been ported to - GPGPUs~\cite{NormMatloff2013ParProcBook,AMD2017OpenCL,NVidia2017GPGPU,NVidia2017GPGPU-university}.} + GPGPUs~\cite{NormMatloff2013ParProcBook,AMD2020ROCm,NVidia2017GPGPU,NVidia2017GPGPU-university}.} \item Operating-system kernels adapted for networking, where each connection (also called \emph{flow}~\cite{Shenker89,ZhangPhD,McKenney90}) is assigned to a specific thread.