mirror/hdf5
2
0
Fork 0
mirror of https://github.com/HDFGroup/hdf5.git synced 2024-11-21 01:04:10 +08:00
Code Issues Packages Projects Releases Wiki Activity

[svn-r2002] Changed 'boot block' to 'super block'.

Browse Source
This commit is contained in:
Frank Baker 2000-03-08 17:03:11 -05:00
parent c0e855bc88
commit fbd9b7f5ad
7 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/html/ExternalFiles.html
View File

@ -64,10 +64,10 @@
<h3>Single Address Space</h3>
<p>The simplest form of hdf5 file is a single file containing only
hdf5 data. The file begins with the boot block, which is
hdf5 data. The file begins with the super block, which is
followed until the end of the file by hdf5 data. The next most
complicated file allows non-hdf5 data (user defined data or
internal wrappers) to appear before the boot block and after the
internal wrappers) to appear before the super block and after the
end of the hdf5 data. The hdf5 data is treated as a single
linear address space in both cases.

2
doc/html/MemoryManagement.html
View File

@ -338,7 +338,7 @@
<p>The file contains an unsorted, doubly-linked list of free
blocks. The address of the head of the list appears in the
boot block. Each free block contains the following fields:
super block. Each free block contains the following fields:
<center>
<table border cellpadding=4 width="60%">

2
doc/html/RM_H5G.html
View File

@ -129,7 +129,7 @@ nodes (nodes with out-degree greater than zero) must be groups
while the leaf nodes (nodes with out-degree zero) are either empty
groups or objects of some other type. Exactly one object in every
non-empty file is the root object. The root object always has a
positive in-degree because it is pointed to by the file boot block.
positive in-degree because it is pointed to by the file super block.
<p>
An object name consists of one or more components separated from

6
doc/html/RM_H5P.html
View File

@ -430,7 +430,7 @@ facilitate moving easily between them.</i>
<dt><strong>Name:</strong> <a name="Property-GetVersion">H5Pget_version</a>
<dt><strong>Signature:</strong>
<dd><em>herr_t </em><code>H5Pget_version</code>(<em>hid_t</em> <code>plist</code>,
<em>int *</em> <code>boot</code>,
<em>int *</em> <code>super</code>,
<em>int *</em> <code>freelist</code>,
<em>int *</em> <code>stab</code>,
<em>int *</em> <code>shhdr</code>
@ -446,8 +446,8 @@ facilitate moving easily between them.</i>
<dl>
<dt><em>hid_t</em> <code>plist</code>
<dd>IN: Identifier of the file creation property list.
<dt><em>int *</em> <code>boot</code>
<dd>OUT: Pointer to location to return boot block version number.
<dt><em>int *</em> <code>super</code>
<dd>OUT: Pointer to location to return super block version number.
<dt><em>int *</em> <code>freelist</code>
<dd>OUT: Pointer to location to return global freelist version number.
<dt><em>int *</em> <code>stab</code>

10
doc/html/compat.html
View File

@ -211,11 +211,11 @@
</tr>
<tr>
<td>User-defined block which is truncated by the size of the
HDF4 file header so that the HDF5 boot block file address
HDF4 file header so that the HDF5 super block file address
doesn't change.</td>
</tr>
<tr>
<td>The HDF5 boot block and data, unmodified by adding the
<td>The HDF5 super block and data, unmodified by adding the
HDF4 wrapper.</td>
</tr>
<tr>
@ -234,9 +234,9 @@
an out of date wrapper.
<p>If there is no user block then we have a problem. The HDF5
boot block must be moved to make room for the HDF4 file header.
But moving just the boot block causes problems because all file
addresses stored in the file are relative to the boot block
super block must be moved to make room for the HDF4 file header.
But moving just the super block causes problems because all file
addresses stored in the file are relative to the super block
address. The only option is to shift the entire file contents
by 512 bytes to open up a user block (too bad we don't have
hooks into the Unix i-node stuff so we could shift the entire

6
doc/html/ddl.html
View File

@ -93,13 +93,13 @@ This section contains a brief explanation of the symbols used in the DDL.
<dir>
<pre>
&lt;file&gt; ::= HDF5 &lt;file_name&gt; { &lt;file_boot_block&gt;<FONT SIZE=1.7>opt</FONT> &lt;root_group&gt; }
&lt;file&gt; ::= HDF5 &lt;file_name&gt; { &lt;file_super_block&gt;<FONT SIZE=1.7>opt</FONT> &lt;root_group&gt; }
&lt;file_name&gt; ::= &lt;identifier&gt;
&lt;file_boot_block&gt; ::= BOOT_BLOCK { &lt;boot_block_content&gt; }
&lt;file_super_block&gt; ::= BOOT_BLOCK { &lt;super_block_content&gt; }
&lt;boot_block_content&gt; ::= TBD
&lt;super_block_content&gt; ::= TBD
&lt;root_group&gt; ::= GROUP "/" { &lt;unamed_datatype&gt;* &lt;object_id&gt;<FONT SIZE=1.7>opt</FONT> &lt;group_attribute&gt;* &lt;group_member&gt;* }

4
doc/html/review1a.html
View File

@ -13,7 +13,7 @@
a directed graph with a single entry point into the graph which
is the <i>Root Object</i>. The root object is usually a
group. All objects have at least one predecessor (the <i>Root
Object</i> always has the HDF5 file boot block as a
Object</i> always has the HDF5 file super block as a
predecessor). The number of predecessors of a group is also
known as the <i>hard link count</i> or just <i>link count</i>.
Unlike Unix directories, HDF5 groups have no ".." entry since
@ -23,7 +23,7 @@
<p>A special optimization is that a file may contain a single
non-group object and no group(s). The object has one
predecessor which is the file boot block. However, once a root
predecessor which is the file super block. However, once a root
group is created it never dissappears (although I suppose it
could if we wanted).