| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix last couple of errors from introducing "regular" hyperslab feature
into the library.
Description:
Code was blindly dereferencing data structures which aren't defined when
operating on regular hyperslabs.
Solution:
Check for regular hyperslab defined and retrieve information from regular
hyperslab info instead of mucking about in other hyperslab information.
Platforms:
Solaris 2.6
|
|
|
|
|
|
|
| |
declaration.
Przemek Klosowski, Ph.D. <przemek@nist.gov> reported this problem on
Linux RH 6.1 systems.
|
|
|
|
|
|
| |
tests are
passing, but not all of them yet...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On my benchmarks,
they are about 4-5 times faster than before. We no longer generate "general"
hyperslab data structures for regular hyperslabs, the general data structures
are only generated when needed for irregular hyperslabs.
Still fixing a couple of nook-and-cranny functions to understand the new
information for the regular hyperslabs, so the tests aren't completely passing,
but I wanted to get this checked in for Elena's benchmarks. I should have
more/all tests passing later today.
|
| |
|
| |
|
|
|
|
| |
autoheader, it was useless to add them in here...
|
|
|
|
|
|
| |
in C++
and, when adding the header to a C++ program, breaks it.
|
|
|
|
|
|
| |
and dynamicly
allocated memory.
|
|
|
|
|
|
|
|
| |
variable instead of
multi-dereferenced pointer chains. This buys us another ~20% improvement in
the hyperslab I/O speed. (From ~30 seconds to ~25 seconds on the h5hypers
benchmark)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fixes
Description:
All tests were core=dumping in IRIX64. The bug is in Generic
property list creation in which malloc asked for 2*64-1 bytes
due to coding bug. The object creation failed but the return
code was not checked. Program eventually crashed.
Solution:
H5F.c:
Check the return code from new file object creation and flag
error accordingly.
H5FL.c:
H5FL_arr_free is a replacement for H5MM_xfree which accepts
null value as a legal argument value. H5FL_arr_free assert
on it. Since other parts of the code have been passing null
value to H5MM_xfree, H5FL_arr_free must accept it too until
all the calling routines are changed to not pass Null.
H5P.c:
some routine passes in 0 as the hashsize value which is uintn.
The expression (hashsize-1) underflows to the largest unsigned
int for some machines. Thus the calloc failed. Cast hashsize
to unsigned int first (this assumes hashsize stays within the
signed int data range.
H5Smpio.c:
Added the extra parameter because the H5FD_write has been redefined.
Platforms tested:
IRIX64 -64 and -n32
|
|
|
|
| |
FAIL...Fixed.
|
|
|
|
|
|
|
|
| |
arrays of
hyperslab boundaries after adding them all, instead of maintaining the sorted
order during each addition. This boosts performance for sub-sampled (i.e.
strided) hyperslabs by about a factor of 10! :-)
|
|
|
|
|
|
| |
garbage collect and
not eat all the memory in the machine (by default :-)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
structures. Also
added code to allow metadata to be allocated out of a more contiguous block
("metadata aggregation") and also code for "catching" small metadata write
calls and building a buffer of the small pieces of metadata for later writing
as one, larger, block ("metadata accumulation"). These features are enabled
on a per VFL driver basis with the new VFL 'query' call and both currently
enabled for the sec2, family and stdio drivers. The mpio VFL driver enables
only the "metadata aggregation" code, not the "metadata accumulation" code.
All the other drivers have these features turned off.
|
|
|
|
|
|
| |
aggregation and
accumulation to be enabled and tracked. Also updated some prototypes.
|
| |
|
|
|
|
|
|
| |
parameter to write
call.
|
|
|
|
|
|
| |
(it's in H5FD.c
now) and updated driver to add the new VFL 'query' call.
|
|
|
|
|
|
| |
field to file
access property lists.
|
| |
|
|
|
|
| |
bytes.
|
|
|
|
|
|
|
| |
set/query the
metadata allocation size for file access property lists. These are new API
functions and should be documented for the next release.
|
|
|
|
|
|
| |
added the
metadata allocation size to the default file access property lists.
|
| |
|
| |
|
|
|
|
|
|
| |
reduce malloc
abuse.
|
|
|
|
|
|
| |
of code, to
get the metadata allocated in the file more tightly together.
|
|
|
|
|
|
| |
logging and added
test code for aggregating metadata into more localized locations in the file.
|
|
|
|
| |
possible.
|
| |
|
|
|
|
| |
warnings.
|
| |
|
|
|
|
|
|
| |
Also, moved
it into the if-then statement to limit it's scope.
|
|
|
|
|
|
| |
compiler
warnings about "implicit cast of pointer to integer" things....
|
|
|
|
|
|
|
|
| |
limits to be
placed on how much memory is used by the free lists before they are garbage
collected. The default is to have no limit, with garbage collection only
occurring when they cannot allocate memory.
|
| |
|
|
|
|
|
|
|
| |
a memory
allocation & attempt to allocate the memory once more. Also re-named a bunch
of private functions & structures to align with other function names.
|
| |
|
|
|
|
|
|
| |
realloc()
calls. Speeds user's test code up by ~25 times... :-)
|
| |
|
|
|
|
| |
calculations.
|
|
|
|
|
|
|
|
| |
collecting the free
lists. Each kind of list one has hard-coded limits on when to garbage collect,
which will be replaced with user-controllable knobs (through property list
settings, I think) once I finish debugging some related performance problems.
|
|
|
|
|
|
| |
yet, but it's
close. This shouldn't interfere with other development work. (I think.. :-)
|
|
|
|
|
|
| |
certain obscure
situations).
|
| |
|
| |
|
| |
|
| |
|