CVS log for pvfs2/src/server/statfs.sm
	Help

Request diff between arbitrary revisions / Display revisions graphically

Merged robust security code into Orange-Branch.

checkpoint, transition to uuids

changes to PVFS_handle_X

change to #defined calls to uuids

migrate from uint64_t type assignments to uuids

initial support for solaris.  doesn't include /dev/epoll support.  See trac ticket #97.

Reverse merged and ported to HEAD.

state machine permission checking code cleanup

Updated security checking in state machines.  Added flags where needed.

modified permission checking to use callbacks instead of flags. added custom
checks to the io and small-io state machines.

Big pile-o' changes to make Pete go mad.

The main changes are the implementation of the stuffed create path (now just the create state machine and operation), and the beginnings of the "unstuff" operation.

This also includes the request scheduler and state machine cleanups (required for using prelude with batch_remove) and whatever else I may have happened to change along the way.

This code is able to create files, but writing to them is almost guaranteed to break.

Sam's prelude and scheduler updates

The normal path for a server request operation is to jump to the prelude state machine, which tries schedule the request based on the handle+fsid.  This meant that the request scheduler code had a switch/case returning the handle+fsid for each request we defined.  The function was also overloaded with a readonly parameter (whether the request modified any objects on the server), and a scheduling policy parameter (as the return code), which specified whether the request scheduling could be bypassed for this request.

I moved all that to a per-request parameter structure, that gets specified within the server state machine for the request.  Now there is one array of server requests (moved to pvfs2-server-req.c) which the request scheduler and prelude state machine can poke at to get parameters (defined in the state machine for that request), and based decisions on.

The patch includes some other minor changes:

* A fix to the BMI addr ref count increment/decrement.  Previously, the addr ref count was being incremented/decremented in the prelude/final-response state machines.  That requires that those state machines get invoked, which I don't want to have to depend on.  I've moved the INC call to the unexpected_sm, and the DEC call to where the state machine gets finished in the server.  That way we don't have to worry about whether we're using prelude/final-response.

* Cleanup of the request scheduler.  The way we were changing the mode from normal to admin was sort of embedded into the request scheduling code, so we had to hack the mode change from prelude_sm instead of in setparam.  Also, the request scheduler had to be aware of the setparam fields in the request.  I've moved the mode change code to separate request scheduler and job calls.  I think something similar could be done for the timer code (it doesn't really belong in the request scheduler), but I'll leave that for another patch.

* Changed the way we compile the server binary in Makefile.in to allow for multiple object files.

minor change allows state actions to not be declared at the top of *.sm files.

Merge HEAD changes to TAS-branch.

merge of the WALT3 branch to HEAD.  This patch changes the way state actions
are represented as C structures (what statecomp generates).  It also changes
the main state action parameter from a s_op on the server or an sm_p on the client
to a unified smcb pointer (state machine control block) for all state actions (both client and server).  Finally, initial support for concurrent state machines has
been added to allow state actions to be invoked concurrently .. a first step for
server-to-server.

walt3 reverse merge from head includes merges of pw's sm changes (no state declarations), cleanup of state machine code, and other general merging/fixes.

update to current CVS version because statecomp modifications are neat for my work, thanks!

Remove forward declarations of states.

Everything compiles.   Crap!  Now I have to see if it runs!!!

removing compile errors

correcting compile errors

updated to support SM control block interface

Reverse merge from trunk to lockd-branch...

reverse merge of branch

merge sync coalescing branch.

fix deadlock bugs in coalescing code.  add proper state machine debugging.

* added event logging for states
* moved state debug code to state-machine so all state start/end
points get debug messages automatically
* added textlog stuff.  This allows us to write the default event
queue out to a text file that can be converted to slog2 later.

retrieve the total number of handles per server in the server state machine
rather than on the client side; avoids serialized iteration through
configuration information and handle extents on client side for N servers

make statfs return load averages from sysinfo()

- added an internal ref_type member to the client state machine object
  so that the callers of the sm_shared_getattr_* methods (which use
  the object_ref or parent_ref internal members) can enforce the
  attribute type before doing the operation they're trying to do.  for
  example, in the error case of trying to do a readdir on a metafile
  (rather than a directory) the previous readdir operation would do a
  getattr and then issue the readdir operation to the server (and get
  an error back from the server because the object type is wrong).
  with this simple type checking in place, the getattr will fail with
  an appropriate error message (in this example case -PVFS_ENOTDIR) so
  that we can avoid the second network round-trip all together.  the
  same goes for I/O and truncate operations (as the objects must be
  metafiles), and create/symlink/mkdir (as the parent MUST be a
  directory).  How are symlinks handled?  they're not -- our sysint
  API calls expect actual handles, never links.  That means that
  callers (i.e. the pvfs2-client, ROMIO, the test programs, etc) will
  have to resolve the link with the appropriate lookup option
  before-hand (this is consistent with what we've been doing so far
  anyway, as added support for symlink type checking doesn't work
  since all operations are not symlink aware -- nor should they be,
  IMO).
- added error handling to crdirent, which would crash the server if a
  non-directory type was passed to it
- misc cleanups on both server and client side

- applied Nathan's expandtab patch (expandtab-2.patch.gz)

  first referenced at:
  http://www.beowulf-underground.org/pipermail/pvfs2-developers/2004-July/000745.html

- keep the statfs object the same, even if sysinfo call isn't available

- add configure test for sys/sysinfo.h (should be on all linux machines)
- add memory and uptime information into the (now ill-named) statfs object
- update pvfs2-statfs to display this newly added information

updated to sm syntax: state machines now allow a special "terminate"
transition to indicate the final state in a state machine.  updated
all state machines accordingly.  statecomp will generate a warning if a
statemachine does not contain at least one "terminate" or "return"
transition.  other related cleanups and sanity checks.

filled in remaining handle statistics in statfs calls; appears to work
but probably needs some testing in the multi server case

started reporting some handle statistics in stat- not right yet

fix compile error

added a new PVFS_statfs structure (incomplete- just a few fields to
start with), implemented trove_collection_getinfo() to retrieve this
information from file system, hooked into server statfs implementation.
completely untested, and no client side support yet

whoops- yeah, I forgot to check this in on friday...