Skip to content

Commit 47966b1

Browse files
CamStanadammoody
authored andcommitted
Docs: update for 1.1 release
1 parent a57ec3b commit 47966b1

File tree

6 files changed

+41
-13
lines changed

6 files changed

+41
-13
lines changed

docs/build.rst

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,10 @@
22
Build UnifyFS
33
=============
44

5-
This section describes how to build UnifyFS and its dependencies.
6-
There are three options:
5+
This section describes how to build UnifyFS and its dependencies, and what
6+
:ref:`configure time options <configure-options-label>` are available.
7+
8+
There are three build options:
79

810
* build both UnifyFS and dependencies with Spack,
911
* build the dependencies with Spack, but build UnifyFS with autotools
@@ -22,7 +24,7 @@ If you use a clone of the Spack develop branch, be sure to pull the latest chang
2224
.. warning:: **Thallium, Mochi Suite, and SDS Repo Users**
2325

2426
The available and UnifyFS-compatible Mochi-Margo versions that are in the
25-
``mochi-margo`` Spack package do not match up with the latest/default
27+
``mochi-margo`` Spack package may not match up with the latest/default
2628
versions in the Mochi Suite, SDS Repo, and ``mochi-thallium`` Spack
2729
packages. It is likely that a different version of ``mochi-margo`` will need
2830
to be specified in the install command of UnifyFS (E.g.: ``spack install
@@ -60,17 +62,18 @@ variants.
6062
.. table:: UnifyFS Build Variants
6163
:widths: auto
6264

63-
========== ============================= ======= ===========================
65+
========== ============================= ======= =================================
6466
Variant Command Default Description
6567
(``spack install <package>``)
66-
========== ============================= ======= ===========================
68+
========== ============================= ======= =================================
6769
Auto-mount ``unifyfs+auto-mount`` True Enable transparent mounting
68-
Boostsys ``unifyfs+boostsys` False Have Mercury use Boost
70+
Boostsys ``unifyfs+boostsys`` False Have Mercury use Boost
6971
Fortran ``unifyfs+fortran`` True Enable Fortran support
7072
PMI ``unifyfs+pmi`` False Enable PMI2 support
7173
PMIx ``unifyfs+pmix`` False Enable PMIx support
74+
Preload ``unifyfs+preload`` False Enable LD_PRELOAD library support
7275
SPath ``unifyfs+spath`` True Normalize relative paths
73-
========== ============================= ======= ===========================
76+
========== ============================= ======= =================================
7477

7578
.. attention::
7679

@@ -219,6 +222,7 @@ after ``./autogen.sh`` has been run.
219222
220223
----------
221224
225+
.. _configure-options-label:
222226
-----------------
223227
Configure Options
224228
-----------------

docs/conf.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@
5454
# built documents.
5555
#
5656
# The short X.Y version.
57-
version = u'1.0.1'
57+
version = u'1.1'
5858
# The full version, including alpha/beta/rc tags.
59-
release = u'1.0.1'
59+
release = u'1.1'
6060

6161
# The language for content autogenerated by Sphinx. Refer to documentation
6262
# for a list of supported languages.

docs/examples.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ build into static, GOTCHA, and pure POSIX (not linked with UnifyFS) versions
77
depending on how they are linked. Several of the example programs are also used
88
in the UnifyFS :doc:`intregraton testing <testing>`.
99

10+
----------
11+
1012
Locations of Examples
1113
=====================
1214

@@ -174,6 +176,8 @@ One form of running this example could be:
174176
175177
$ srun -N4 -n4 write-static -m /unifyfs -f myTestFile
176178
179+
----------
180+
177181
Producer-Consumer Workflow
178182
==========================
179183

docs/limitations.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,8 @@ Directory Operations
5656

5757
UnifyFS does not support directory operations.
5858

59+
----------
60+
5961
---------------------------
6062
MPI-IO Limitations
6163
---------------------------
@@ -151,6 +153,8 @@ standard and execute a full sync-barrier-sync construct.
151153
There exist potential optimizations such that
152154
future implementations of UnifyFS may require the full sequence of calls.
153155

156+
----------
157+
154158
---------------------------
155159
ROMIO Limitations
156160
---------------------------
@@ -272,6 +276,8 @@ Functions that use shared file pointers include::
272276
MPI_File_write_ordered()
273277
MPI_File_read_ordered()
274278

279+
----------
280+
275281
---------------------------
276282
HDF5 Limitations
277283
---------------------------
@@ -328,6 +334,8 @@ environment variable ``HDF5_DO_MPI_FILE_SYNC=1``.
328334
Enabling this option can decrease write performance
329335
since it may induce more file flush operations than necessary.
330336

337+
----------
338+
331339
-------------------
332340
PnetCDF Limitations
333341
-------------------

docs/link.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ The UnifyFS library contains symbols for the UnifyFS API, like unifyfs_mount,
77
as well as wrappers for I/O routines, like open, write, and close.
88
In the examples below, replace <unifyfs> with the path to your UnifyFS install.
99

10-
---------------------------
10+
----------
1111

1212
-----------
1313
Static link
@@ -25,6 +25,8 @@ To make this easier, UnifyFS installs a unifyfs-config script that one should in
2525
test_write.c \
2626
`<unifyfs>/bin/unifyfs-config --post-ld-flags`
2727
28+
----------
29+
2830
------------
2931
Dynamic link
3032
------------

docs/run.rst

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ Overall, the steps to run an application with UnifyFS include:
1717

1818
5. Terminate the UnifyFS servers using ``unifyfs``
1919

20+
----------
21+
2022
-------------
2123
Start UnifyFS
2224
-------------
@@ -95,6 +97,8 @@ Only applications that explicitly call ``unifyfs_mount()`` and access files
9597
under the specified mountpoint prefix will utilize UnifyFS for their I/O. All
9698
other applications will operate unchanged.
9799
100+
----------
101+
98102
------------
99103
Stop UnifyFS
100104
------------
@@ -104,6 +108,8 @@ After all UnifyFS-enabled applications have completed running, use
104108
``unifyfs start`` to have the servers remove temporary data locally stored on
105109
each node after termination.
106110
111+
----------
112+
107113
--------------------------------
108114
Resource Manager Job Integration
109115
--------------------------------
@@ -121,9 +127,11 @@ within the source repository at ``util/scripts/lsfcsm``.
121127
122128
Support for the SLURM resource manager is under development.
123129
124-
-----------------------------------------
130+
----------
131+
132+
---------------------------------------
125133
Transferring Data In and Out of UnifyFS
126-
-----------------------------------------
134+
---------------------------------------
127135
128136
Data can be transferred in/out of UnifyFS during server startup and termination,
129137
or at any point during a job using two stand-alone applications.
@@ -254,9 +262,11 @@ Examples:
254262
255263
$ srun -N 4 -n 8 unifyfs-stage --parallel $MY_MANIFEST_FILE
256264
265+
----------
257266
267+
---------------------
258268
UnifyFS LS Executable
259-
^^^^^^^^^^^^^^^^^^^^^^^^
269+
---------------------
260270
261271
The ``unifyfs-ls`` program is installed in the same directory as the
262272
``unifyfs`` utility (i.e., ``$UNIFYFS_INSTALL/bin``). This tool will provide

0 commit comments

Comments
 (0)