public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nicolas Bock <nicolasbock@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci-physics/lammps: question on proper integration of mpi
Date: Mon, 13 May 2013 10:22:20 -0600	[thread overview]
Message-ID: <CAPMKG4DsMARP4T3GPDg-OEnmwKVQHJVCVxjsFHHYoY0WXVz2Rg@mail.gmail.com> (raw)
In-Reply-To: <CANgp9kzgT=AVpKYHLz8Os1WODrstpuMRrxCPuqDo=Mxm5uOGUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]

Hi Christoph,

thanks for the detailed answer. I have made a few changes to the ebuild,
implementing what you suggested. The only thing missing right now is a
better way to deal with the Makefile. I am working on that. In the meantime
I have created a pull request.

Thanks again,

nick



On Sun, May 12, 2013 at 5:08 PM, Christoph Junghans <ottxor@gentoo.org>wrote:

> Hi Nick,
>
> thanks for your contribution.
>
> I think there is no general answer to your question. It depends if it
> is a disadvantage of running the mpi-version with 1 MPI process over
> running the serial version. I imagine that LAMMPS enable some special
> optimization if mpi is disabled as it can assume that everything
> happens locally and no mpi message need to be send. On the other hand,
> if the build of LAMMPS takes hours, one might prefer building it only
> once. Do LAMMPS offer other palatalizations like OpenMP or Threads to
> use multiple cores?
>
> From a brief look at our patch I see the following issues:
> - I am not sold on this Makefile patch and patching of the patch
> approach, seems a bit fragile. It might be better to use the default
> gcc Makefile and patch that. I prefer adding CC,CFLAGS etc, on emake
> comandline, you could create a function to avoid writing it on every
> emake call. (my_emake() { emake "$@" CC= CFLAGS=; } )
> - sed calls need to secured with "|| die"
> - DEPEND should be static, DEPEND="mpi? ( vitrual/mpi )" should do it
> - virtual/fortran is missing in DEPEND or use fortran-2.eclass and
> FORTRAN_NEEDED="fortran" instead.
> - lammps-gzip enables normal gzip support, so the use flags should be
> called gzip.
>
> If you are unsure about some technical details in an ebuild, create a
> pull request on github and somebody will give you advice in the
> review.
>
> Otherwise good job, looking forward to more commits from you,
>
> Christoph
>
> 2013/5/12 Nicolas Bock <nicolasbock@gmail.com>:
> > Hi,
> >
> > I recently added a lammps ebuild to the science overlay. It so far only
> > builds the serial version, and has very limited support for build time
> > options. I now added the mpi use flag and changed the ebuild so that it
> > builds the mpi version. I have attached a patch against master that does
> > this. I would like to get some feedback on those changes. Are they
> > acceptable in this form? What should I have done differently? How would
> I go
> > about writing an ebuild that builds both, the serial _and_ the mpi
> version
> > in case the mpi use flag is set?
> >
> > Thanks already,
> >
> > nick
> >
>
>
>
> --
> Christoph Junghans
> http://dev.gentoo.org/~ottxor/
>
>

[-- Attachment #2: Type: text/html, Size: 3526 bytes --]

      reply	other threads:[~2013-05-13 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 21:22 [gentoo-science] sci-physics/lammps: question on proper integration of mpi Nicolas Bock
2013-05-12 23:08 ` Christoph Junghans
2013-05-13 16:22   ` Nicolas Bock [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPMKG4DsMARP4T3GPDg-OEnmwKVQHJVCVxjsFHHYoY0WXVz2Rg@mail.gmail.com \
    --to=nicolasbock@gmail.com \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox