diff options
| author | Frank Baker <fbaker@hdfgroup.org> | 2005-07-19 17:28:56 (GMT) |
|---|---|---|
| committer | Frank Baker <fbaker@hdfgroup.org> | 2005-07-19 17:28:56 (GMT) |
| commit | 794ba0a251af47b8e3c60afa2fe92d267e2a6b55 (patch) | |
| tree | f24cea3b81ff02fa3f31c0a1c4e80fa10f4393c0 /doc/html/move.html | |
| parent | d2e92fd23610c3ccdddbbc55484e54a5a21a9252 (diff) | |
| download | hdf5-794ba0a251af47b8e3c60afa2fe92d267e2a6b55.zip hdf5-794ba0a251af47b8e3c60afa2fe92d267e2a6b55.tar.gz hdf5-794ba0a251af47b8e3c60afa2fe92d267e2a6b55.tar.bz2 | |
[svn-r11084]
Description:
All HDF5 user documentation has been moved to a separate hdf5doc/
repository, managed under Subversion.
With this 'cvs commit', all files are stripped from hdf5/doc/.
THIS CHANGE IS APPLIED ONLY TO THE HDF5 DEVELOPMENT BRANCH,
post Release 1.6.x; it is not applied to the release branches.
Diffstat (limited to 'doc/html/move.html')
| -rw-r--r-- | doc/html/move.html | 66 |
1 files changed, 0 insertions, 66 deletions
diff --git a/doc/html/move.html b/doc/html/move.html deleted file mode 100644 index ec87d11..0000000 --- a/doc/html/move.html +++ /dev/null @@ -1,66 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> -<html> - <head> - <title>How to Relocate a File Data Structure</title> - </head> - - <body> - <h1>How to Relocate a File Data Structure</h1> - - <p>Since file data structures can be cached in memory by the H5AC - package it becomes problematic to move such a data structure in - the file. One cannot just copy a portion of the file from one - location to another because: - - <ol> - <li>the file might not contain the latest information, and</li> - <li>the H5AC package might not realize that the object's - address has changed and attempt to write the object to disk - at the old address.</li> - </ol> - - <p>Here's a correct method to move data from one location to - another. The example code assumes that one is moving a B-link - tree node from <code>old_addr</code> to <code>new_addr</code>. - - <ol> - <li>Make sure the disk is up-to-date with respect to the - cache. There is no need to remove the item from the cache, - hence the final argument to <code>H5AC_flush</code> is - <code>FALSE</code>. - <br><br> - <code> - H5AC_flush (f, H5AC_BT, old_addr, FALSE);<br> - </code> - <br> - </li> - - <li>Read the data from the old address and write it to the new - address. - <br><br> - <code> - H5F_block_read (f, old_addr, size, buf);<br> - H5F_block_write (f, new_addr, size, buf);<br> - </code> - <br> - </li> - - <li>Notify the cache that the address of the object changed. - <br><br> - <code> - H5AC_rename (f, H5AC_BT, old_addr, new_addr);<br> - </code> - <br> - </li> - </ol> - - - - <hr> - <address><a href="mailto:robb@maya.nuance.com">Robb Matzke</a></address> -<!-- Created: Mon Jul 14 15:09:06 EST 1997 --> -<!-- hhmts start --> -Last modified: Mon Jul 14 15:38:29 EST -<!-- hhmts end --> - </body> -</html> |