September 2015 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Sean Farley 30 Sep '15

30 Sep '15

Jed Brown <jed(a)jedbrown.org> writes: > Barry Smith <bsmith(a)mcs.anl.gov> writes: > >>> On Sep 30, 2015, at 9:48 AM, Jed Brown <jed(a)jedbrown.org> wrote: >>> >>> Matthew Knepley <knepley(a)gmail.com> writes: >>>> Richard, this is somewhat subtle since PETSc's inheritance model is sucky >>>> and somewhat broken. Look at >>>> the factorization classes, AIJMUMPS etc., before coding anything. >>> >>> Richard wants to use the MKL implementations of stuff like MatMult and >>> MatAXPY, not just factorization. So it doesn't look like AIJMUMPS. >> >> Jed and Matt, >> >> Remember Richard actually wrote the subclasses of AIJ for the Cray vector machine so you guys are teaching your grandmother to suck eggs. > > Where is @shitbsmithsays when you need it? Soon. Very soon.

1 0

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Barry Smith 30 Sep '15

30 Sep '15

> On Sep 30, 2015, at 2:47 PM, Jed Brown <jed(a)jedbrown.org> wrote: > > Satish Balay <balay(a)mcs.anl.gov> writes: >> What you are suggesting is merge mkl_pardiso.py, mkl_pardiso.py [and >> mkl_spmv2.py] into a single mkl.py - and then add in the support for >> these features inside it. > > That's one implementation. > >> --with-mkl-dir=LOCATION_OF_INTEL_MKL --with-mkl-pardiso=1 --with-mkl-cpardiso=1 --with-mkl-spmv2=1 > > I prefer this user interface. This is fine and can be done with a mkl.py file, mkl_pardiso.py file etc. Barry

1 0

Re: [petsc-dev] http://m.vtk.org/index.php/Main_Page
by Matthew Knepley 30 Sep '15

30 Sep '15

On Wed, Sep 30, 2015 at 2:41 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > > On Sep 30, 2015, at 2:31 PM, Matthew Knepley <knepley(a)gmail.com> wrote: > > > > On Wed, Sep 30, 2015 at 2:24 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > > > Worth adding viewer for it? > > > > I assume it can read VTK. Also > > > > VTK-m is written in C++ and makes extensive use of templates. The > toolkit is implemented as a header library, meaning that all the code is > implemented in header files (with extension .h) and completely included in > any code that uses it. > > > > so, no I don't want any of that code :) > > I asked them to add a C interface. > Wait, then we would lose the traits. THE TRAITS!!! Matt > Barry > > > > > Matt > > > > -- > > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > > -- Norbert Wiener > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Jed Brown 30 Sep '15

30 Sep '15

Satish Balay <balay(a)mcs.anl.gov> writes: > What you are suggesting is merge mkl_pardiso.py, mkl_pardiso.py [and > mkl_spmv2.py] into a single mkl.py - and then add in the support for > these features inside it. That's one implementation. > --with-mkl-dir=LOCATION_OF_INTEL_MKL --with-mkl-pardiso=1 --with-mkl-cpardiso=1 --with-mkl-spmv2=1 I prefer this user interface.

1 0

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Barry Smith 30 Sep '15

30 Sep '15

> On Sep 30, 2015, at 2:38 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > On Wed, 30 Sep 2015, Jed Brown wrote: > >> Satish Balay <balay(a)mcs.anl.gov> writes: >>> I think the issue was - blaslapack.py [as is currently organized] does >>> not need or care for mkl.h. But mkl_cpardiso.py requires it. For >>> mkl_cpardiso.py to find it - it requires the -dir - or include/lib >>> options. >> >> Can one use mkl_pardiso with a different BLAS/Lapack? If not, maybe >> --with-mkl-dir= or some such to avoid repetition of the ridonculous >> paths. > > What you are suggesting is merge mkl_pardiso.py, mkl_pardiso.py [and > mkl_spmv2.py] into a single mkl.py - and then add in the support for > these features inside it. > > --with-mkl-dir=LOCATION_OF_INTEL_MKL --with-mkl-pardiso=1 --with-mkl-cpardiso=1 --with-mkl-spmv2=1 No, each gets their own file but they use the blas/lapack directory as the directory to look for stuff. Barry > > [or autodetect pardiso, cpardiso spmv2 etc..] > > perhaps this is possible.. > > Satish >

1 0

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Satish Balay 30 Sep '15

30 Sep '15

On Wed, 30 Sep 2015, Satish Balay wrote: > On Wed, 30 Sep 2015, Jed Brown wrote: > > > Satish Balay <balay(a)mcs.anl.gov> writes: > > > I think the issue was - blaslapack.py [as is currently organized] does > > > not need or care for mkl.h. But mkl_cpardiso.py requires it. For > > > mkl_cpardiso.py to find it - it requires the -dir - or include/lib > > > options. > > > > Can one use mkl_pardiso with a different BLAS/Lapack? If not, maybe > > --with-mkl-dir= or some such to avoid repetition of the ridonculous > > paths. > > What you are suggesting is merge mkl_pardiso.py, mkl_pardiso.py [and > mkl_spmv2.py] into a single mkl.py - and then add in the support for > these features inside it. > > --with-mkl-dir=LOCATION_OF_INTEL_MKL --with-mkl-pardiso=1 --with-mkl-cpardiso=1 --with-mkl-spmv2=1 > > [or autodetect pardiso, cpardiso spmv2 etc..] > > perhaps this is possible.. BTW: cpardiso probably needs intel MPI? [that part is not properly encoded in mkl_cpardiso.py yet..] Satish

1 0

Re: [petsc-dev] http://m.vtk.org/index.php/Main_Page
by Barry Smith 30 Sep '15

30 Sep '15

> On Sep 30, 2015, at 2:31 PM, Matthew Knepley <knepley(a)gmail.com> wrote: > > On Wed, Sep 30, 2015 at 2:24 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > Worth adding viewer for it? > > I assume it can read VTK. Also > > VTK-m is written in C++ and makes extensive use of templates. The toolkit is implemented as a header library, meaning that all the code is implemented in header files (with extension .h) and completely included in any code that uses it. > > so, no I don't want any of that code :) I asked them to add a C interface. Barry > > Matt > > -- > What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. > -- Norbert Wiener

1 0

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Satish Balay 30 Sep '15

30 Sep '15

On Wed, 30 Sep 2015, Jed Brown wrote: > Satish Balay <balay(a)mcs.anl.gov> writes: > > I think the issue was - blaslapack.py [as is currently organized] does > > not need or care for mkl.h. But mkl_cpardiso.py requires it. For > > mkl_cpardiso.py to find it - it requires the -dir - or include/lib > > options. > > Can one use mkl_pardiso with a different BLAS/Lapack? If not, maybe > --with-mkl-dir= or some such to avoid repetition of the ridonculous > paths. What you are suggesting is merge mkl_pardiso.py, mkl_pardiso.py [and mkl_spmv2.py] into a single mkl.py - and then add in the support for these features inside it. --with-mkl-dir=LOCATION_OF_INTEL_MKL --with-mkl-pardiso=1 --with-mkl-cpardiso=1 --with-mkl-spmv2=1 [or autodetect pardiso, cpardiso spmv2 etc..] perhaps this is possible.. Satish

1 0

Re: [petsc-dev] http://m.vtk.org/index.php/Main_Page
by Matthew Knepley 30 Sep '15

30 Sep '15

On Wed, Sep 30, 2015 at 2:24 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > Worth adding viewer for it? > I assume it can read VTK. Also VTK-m is written in C++ and makes extensive use of templates. The toolkit is implemented as a header library, meaning that all the code is implemented in header files (with extension .h) and completely included in any code that uses it. so, no I don't want any of that code :) Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] Adding support for new sparse BLAS inspector-executor routines in MKL
by Jed Brown 30 Sep '15

30 Sep '15

Satish Balay <balay(a)mcs.anl.gov> writes: > I think the issue was - blaslapack.py [as is currently organized] does > not need or care for mkl.h. But mkl_cpardiso.py requires it. For > mkl_cpardiso.py to find it - it requires the -dir - or include/lib > options. Can one use mkl_pardiso with a different BLAS/Lapack? If not, maybe --with-mkl-dir= or some such to avoid repetition of the ridonculous paths.

1 0