[mpich-discuss] MPI_Win_fence memory consumption

[Rajeev Thakur]

OK, thanks. We will look into it.

Rajeev 

> -----Original Message-----
> From: mpich-discuss-bounces at mcs.anl.gov 
> [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Dorian Krause
> Sent: Friday, February 27, 2009 7:44 PM
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [mpich-discuss] MPI_Win_fence memory consumption
> 
> Rajeev Thakur wrote:
> > Does that happen only with Nemesis or even with ch3:sock?
> >   
> 
> The behaviour is the same with the configure flag 
> --with-device=ch3:sock.
> 
> Dorian
> 
> > Rajeev
> >
> >   
> >> -----Original Message-----
> >> From: mpich-discuss-bounces at mcs.anl.gov 
> >> [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of 
> Dorian Krause
> >> Sent: Friday, February 27, 2009 7:16 AM
> >> To: mpich-discuss at mcs.anl.gov
> >> Subject: [mpich-discuss] MPI_Win_fence memory consumption
> >>
> >> Hi List,
> >>
> >> the attached test program uses 
> MPI_Accumulate/MPI_Win_fence for one 
> >> sided communication with derived datatype.
> >> The program runs fine with mpich2-1.1a2 except for my debugging 
> >> version of MPICH2 compiled with
> >>
> >> ./configure --with-device=ch3:nemesis --enable-g=dbg,mem,meminit
> >>
> >> In this case the MPI_Win_fence on the target side comuses 
> about 90% 
> >> of main memory (e.g. > 3 GB). As the behaviour is completely 
> >> different for predefined datatypes, I suspect that the memory 
> >> consumption is related to the construction of the derived 
> datatype on 
> >> the target side.
> >>
> >> Is there a workaround for this?
> >>
> >> Thanks + Best regards,
> >> Dorian
> >>
> >>
> >>
> >>
> >>
> >>     
> 
>