#73: Add installcheck target
--------------------------+-------------------------------------------------
Reporter: dkimpe | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: later
Component: Build system | Keywords:
--------------------------+-------------------------------------------------
Once package-config is working, test compiling and linking a test program
from the install-check target.
{{{
http://www.gnu.org/software/hello/manual/automake/Standard-Targets.html
}}}
--
Ticket URL: <http://trac.mcs.anl.gov/projects/iofsl/ticket/73>
iofsl <http://trac.mcs.anl.gov/projects/iofsl>
I/O Forwarding Scalability Layer
#65: fix compilation using intel compiler
------------------------------------------------+---------------------------
Reporter: dkimpe | Owner:
Type: problems building or running IOFSL | Status: new
Priority: minor | Milestone: later
Component: Forwarding Server | Keywords:
------------------------------------------------+---------------------------
Intel compiler gives an error and a whole bunch of warnings (tested on
fusion)
--
Ticket URL: <http://trac.mcs.anl.gov/projects/iofsl/ticket/65>
iofsl <http://trac.mcs.anl.gov/projects/iofsl>
I/O Forwarding Scalability Layer
#64: change tag selection mechanism in client
-----------------------+----------------------------------------------------
Reporter: anonymous | Type: enhancement
Status: new | Priority: minor
Milestone: later | Component: ZOIDFS FUSE client
Keywords: |
-----------------------+----------------------------------------------------
the client currently uses pthread_self() to pick a tag. This makes it
impossible to restrict the tag range;
Using TLS helps with this (incrementing the tag number for each new thead)
but this will overflow and conflict once enough threads have been created
(even if they are not being used concurrently).
For example, if the main thread (tag 1) makes zoidfs calls and then
repeatedly generates a thread for each zoidfs operation the tag counter
will eventually overflow, causing both the main thread and the new thread
to use tag 1.
A better solution seems to be to use OpenPA and atomically increment the
tagnumber on each operation; However, the client currently assumes
gen_tag() always returns the same value for the same thread.
This needs to be fixed before the scheme above can be implemented.
This fix is also needed for async operations, once they are added.
--
Ticket URL: <http://trac.mcs.anl.gov/projects/iofsl/ticket/64>
iofsl <http://trac.mcs.anl.gov/projects/iofsl>
I/O Forwarding Scalability Layer
HI,
There has been a host of problems with emailing test results from a
machine at LANL to the relevant parties of the IFOSL development team.
These problems are being addressed.
As of now I am attempting to correctly cc developers at ANL, and mail
directly to the io-fwd-discuss(a)lists.mcs.anl.gov address.
Hopefully changes that were made this morning will address this problem.
I'm also contacting HPC support at LANL to see if there is any changes
that can be made to make mailing mcs.anl.gov possilbe. I'll let you know
about the status of these changes when they do or do not happen.
Typically the HPC department will not change anything with the machines
due to system security.
Thanks,
Rico
