H5Part development and discussion

[Mark Howison <MHowison AT lbl.gov>]

Hi Achim,

I'm still working through the H5Block code, and I wanted to find out
more about the original design decisions for handling arbitrary ghost
zones, which introduces alot of complexity in "dissolving" them. I
don't see an easy way to get around the O(n) space required in the
H5Block file struct to store every proc's field layout for use in the
ghost zone routines. Do we need to support arbitrary ghost zones? Is
there a simpler way to handle them? I think if we had some additional
information, like which procs are neighbors, we could drastically
reduce the calculations/space required, but this would mean asking the
user to provide more information.

Mark