CVS log for pvfs2/src/io/trove/trove.h
	Help

Request diff between arbitrary revisions / Display revisions graphically

uuid converstation, PVFS_x_position changes, server/client side first pass done

checkpoint on the uuid road

move PVFS_ds_position to different types when appropriate, pass a flag around instead of using special canary values in the handle. Things will be broken for a while.

Added DeferSyncToShutdown option, which completely diables any possible
calls to fdatasync or db->sync() while PVFS is running.

Add a "type" field to keys in the keyval database so both directory
entries and attributes can be stored for dirdata handles.

Merged in changes from Orange-Branch. There were a number of bugs fixed there since this branch was created.

merge with Orange-Branch

initial transactional bdb work

Bump Trove DBPF version for new precreate-handle storage format. Include migration to 0.1.5. Add job_trove_fs_del_eattr() function and associated lower level calls

initial merge with Orange-Branch. much will be broken

removed anything and everything related to certificates

bug and memory fixes to getvalue operation

checkpoint

Merge with work from this summer.  Metadata and data storage spaces can now be located on different disks.  Fixed a small bug in string encoding.  Updated test code to reflect new Trove dual-storage space API.  Genconfig updated as well as affected admin apps. In the correct branch this time.

Undo accidental commit to MAIN.  Reverted each file to pre-commit version.

Merge with work from this summer.  Metadata and data storage spaces can now be located on different disks.  Fixed a small bug in string encoding.  Updated test code to reflect new Trove dual-storage space API.  Genconfig updated as well as affected admin apps.

merged in changes from summer at LANL

get-path implemenation work

initial get-path state machine and associated changes

Merge range query changes and other fixes

Initial import of branch supporting keyval attribute/value lookup

- Change the Trove version to 0.1.4
- Implemented trove_migrate() to update database from 0.1.3 to 0.1.4
- Migration from 0.1.3 to 0.1.4 stats existing bstreams and
  updates the b_size attribute in the database.

Properly shutdown trove collections that have different methods than the global method.  For example, filesystems specified with directio need to call the directio cleanup to shutdown the threads involved.

adding config options for direct io stuff.

merging hints/events code into trunk.

reverse merge from HEAD.

reverse merge of changes to HEAD since branch.  Includes small file changes.

Merging small files branch to head.  Includes server side precreation of
data files and file stuffing.

dspace, keyval, coll_attr dbs are now created within the environment.
A whole lot of other things try to make replication work

db-replication state machine which processes the incomming replication message

Add a seperate thread to handle the db_rep_send sm. Add the server db replication sm.

db-rep-send state machine added

Reverse merged and ported to HEAD.

use transactional db. db_log_buffer_size and db_log_directory are added into configuration options. shm_key has an error

dspace_remove_list operation for trove; untested

hints and events.

a completely untested dspace_create_list() operation to allow multiple
handles to be created with one trove call

give keyval iterate functions the ability to remove keys as they go;
untested

add support for binary keys to trove; untested

inode stuffing operation.  also added a keyval_remove_list.

Update migration branch to current CVS version

Upgrade to current CVS version

reverse merge of HEAD to WALT3 branch.

commit of trove method capabilities.  We should now be able to support multiple trove methods.  The TroveMethod option to the config file can set the method to something other than the default (dbpf).

hint is given down to Trove

backmerging of HEAD to branch...

Merge HEAD into Walt's branch.
Rework new state machines to the new cleanups introduced by Walt.

Merge posix-extensions-branch to HEAD
This branch implemented patches to the 2.6.16 kernel for the proposed POSIX I/O extensions and those patches are under
the patches subdirectory.
It also implements the PVFS2 specific hooks for these system calls.

Tools that may be of immediate use to the pvfs2 general audience is the pvfs2-lsplus utility in src/apps/admin
that should be noticeably faster than the pvfs2-ls utility if there are a lot of objects in a single directory.
Other features are left out by configure and are not even built if the kernels do not support those features
and callbacks.

Merge from HEAD to posix-extensions-branch...
This should facilitate merging the posix branch to HEAD...

Implement root squash, read only and all squash export options. All of these are server-side
settings and set in the fs.conf files.. Perhaps the docs need to be pushed out to the pvfs.org website
after this check in?
Wild cards and mask-based addresses are allowed as part of the fs.conf export settings..

Also added a mount time option to honor setuid bit in files, mount -o suid...

Removed the -c option from pvfs2-ping and made the config file checks default.

Alternative Trove implementation branch with Trove transaction support for db >= 4.3.

Reverse merges from HEAD..

reverse merge from trunk.  working for now.

[phil]: flow-proto-tuning: This patch adds "FlowBufferSizeBytes" and "FlowBuffersPerFlow" options to the configuration file format.  They allow you to specify the buffer size that the default flow protocol will use as well as the maximum number of buffers to use per flow.  Note that if you change either of these parameters, then you need to remount any active clients so that they pick up the configuration change before performing any I/O.

[phil]: max-aio: This patch adds "TroveMaxConcurrentIO" to the configuration file format.  It allows you to specify the maximum number of I/O operations that trove will allow to proceed concurrently (currently 16).  Note from the previous email regarding AIO that depending on your access pattern, AIO may queue all of your operations anyway regardless of this setting.  It probably doesn't have much effect unless you are accessing more than one file at a time, or if you are using an alternative to the stock AIO implementation.

[phil]: alternative lio_listio implementation that spawns a thread and does pwrite/pread.

[phil]: bmi-socket-close: This fixes a bug in the new BMI_set_info(... BMI_TCP_CLOSE_SOCKET ...) mechanism, which is used to reconnect the socket to the initial configuration server if new socket buffer sizes are specified in the config file.  I didn't follow the code path find the exact problem, but at a high level it wasn't being thorough enough in cleaning out the old socket.  This showed up when using epoll and specifying socket buffer sizes in the server configuration- in this case the client will often fail to mount with a cryptic "not a directory" error and leave some epoll() errors in the pvfs2-client.log file.  I think a stale (or possibly reused) file descriptor was being left in the epoll fd set.  At any rate, the fix is to use a different set of functions for tearing down the entire address etc. so that it is reconnected on the next BMI addr lookup.  This path is already used by the server to discard old BMI addresses after critical errors on addresses that cannot be reconnected.  It is triggered from bmi.c without entering the bmi_tcp module, so this patch also adds a check to make sure we don't bother for non-tcp methods.

[phil]: bmi-test-overflow: One of the bmi bandwidth test programs was using types that might overflow if testing large enough transfers.  The fix is to convert to doubles and drop in several type casts to be cautious when performing the computation that was causing trouble.

[phil]: cancel-bugs: The biggest fix here is a change to the job timer code.  It was performing some pointer operations in the wrong order, which could lead to job timers failing to trigger in some cases. This would prevent some operations from ever timing out.  A secondary fix is a minor cleanup in BMI to catch potential race conditions in cancellation where a lock wasn't being held while checking to see if the target operation is complete.

[phil]: flow-post-error: This patch adds checks in the client side I/O state machine to test for failure at post time for flow operations.  This type of error is uncommon unless the flow parameters are faulty, but it should have checked anyway to be safe.

[phil]: dfile-config-check: This is a safety test.  The problem here is that there was no bounds checking for the DefaultNumDFiles option in the config file.  This made it possible to select -1 (which in PVFS1 meant "use the default number").  In PVFS2 this number gets passed verbatim to the client and would cause malloc failures and various other odd results when used. The patch just checks at parse time to make sure the value isn't negative.

[phil]: bmi-flow-logging: This patch just adds a little bit more gossip logging output to BMI and the flow protocol.  In particular, it adds tag information to messages about BMI operations, and adds pointer information to the flow protocol to help match posts and completions of flows in log files.

[phil]: server-freopen: This patch just removes duplicate calls to fdreopen(stdin/stdout/stderr) that were being performed on server startup when the server is run in the background.  The first set should be sufficient.

Reverse merge changes from HEAD to posix-extensions-branch.

configure option --enable-aio determines if aio or dbpf-threaded (new)
is used... dbpf-bstream-threaded.c contains threaded I/O version.
This file need some revision... It will be used for testing O_DIRECT.

Checkin of previous patches

Julian's changes to coalescing and dbpf storage options:

- Changes the coalesce code, now we decide the mode (coalesce or not) during
the coalesce function call and not during the enque process.
- Add the coalesce high / low watermark to the dbpf_collection structure, so
colls can have different values.
- Put per default the TROVE_SYNC flag into trove from different statemachines
where we used the macro before. The macro is still there and should be
removed if we agree to this behavior.
- Removes the coalesce config option
- Moves SMALL_IO_MAX_REGIONS to internal and renames it to IO_MAX_REGIONS (we
had it at least 3 times defined somewhere).

merge of murali's changes from trunk.

[pcarns]: Patch to allow modifying distribution, distribution parameters and number of
data files to use within a given directory. Such setting will only impact creation of future files
within the same directory. It does not change existing files' parameters. All such hints
are inherited by newly created directories as well..
[pcarns]: Allow trove to continue to read a list of xattrs/keyvals
without stopping if some subset of keys dont exist in the keyval db. Modifies the keyval_read_list() function
to return an array of completely independant error codes for each key that is read.
[pcarns]: adjust encode_string() macro to make it safe to call on NULL strings
[pcarns]: bug in the getattr state machine that would cause it to read dirent_count most of the time
regardless of whether the attribute mask requested it or not.
[slang]: fix a couple of bugs in the get-attr server-side state machine whereby the dirent_count was being read
using the dirent handle instead of the dirdata handle. Fixed a return value from dbpf_keyval_get_handle_info_op_svc
so that get-attr would not needlessly hang..
[vilayann]: fixes for the viewdist utility yet again, since the keys for the xattrs have changed...

reverse merge of recent bug fixes from trunk

commit of keyval handle info changes.  This allows info to be stored on a per handle basis in a 'null key' inside the database.  Right now we just use it to store the count of directory entries, so that we don't have to do a read/modify/write in crdirent and rmdirent.

Also includes changes to the keyval strings to use #define values instead of the actual strings.  This just makes that code lest prone to bugs in the future.

[phil] see http://www.beowulf-underground.org/pipermail/pvfs2-developers/2006-June/002128.html.

Reverse merge from trunk to lockd-branch...

reverse merge of branch

merge sync coalescing branch.

When TroveSyncMeta is disabled, databases need to be synced periodically.  Instead of using a timer to perform a sync periodically, we use the new sync coalescing code to allow a sync to occur only in cases where the server is experiencing low load.  Basically, the sync operations are coalesced, but the response from the server is returned immediately.  Once the number of operations queued drops below the low watermark, this signals that the coalesced operations should be synced.  This is controlled via the options in the config file:

With TroveSyncMeta set to 'no', the responses from metadata operations are returned immediately, independent of whether an operation triggers a sync of the databases or not, and the following are the default:

CoalescingHighWatermark infinity
CoalescingLowWatermark  1

With this configuration, we never sync under high-load, and wait till the server idles to sync.  Alternative configurations with TroveSyncMeta set to no might be:

CoalescingHighWatermark 50
CoalescingLowWatermark 0

In this configuration, we sync after every 50 operations.  The sync may occur while the server is still under heavy load servicing metadata operations.  Also, there is no timeout between metadata operations before a sync.

reverse merge of trunk to branch

* [Phil] removed db stat left over from keyval-per-db days
* [Phil] added stranded bstream checking
* [Phil] added comparison function for dspace db
* [Phil] added db cache size and type config options

* [Julian] added tcp send/recv buffer size options

First cut of the sys_readdirplus implementation where clients can issue a single
system interface call to get the directory entries as well as the attribute information
of the directory entries.
What this means is that we do not need to call a sys_getattr of the individual directory entries
anymore.
(The kernel version is still untested and won't work until the VFS patch is in place! :))

On the server, there is now a new request/state machine called listattr(poor name, i know!)
which essentially does a vectored getattr for a list of handles as opposed to a getattr
which only does for 1. Perhaps, we need to consolidate them into 1 at a later point of time after
others have given this code a look-see!
On the client, there is a new system interface, and a corresponding statemachine implementation
called readdirplus which does the following algorithm
a) Step 1 - Do a regular readdir
b) Step 2 - Collate all meta handles (obtained from the readdir) and send out 1 listattr
to every server that owns atleast 1 handle from the set.
c) Step 3 - Handles that refer to metafiles (determined by the attributes of the response)
need an additional step to retrieve their file sizes. So we collate all data file handles
of all metafiles, and send out 1 listattr to every server that owns atleast 1 handle from
the set.
d) Step 4 - Copy object attributes obtained for all objects into the sys response structure and
also compute file sizes of regular files since we know the individual dfile handles' file sizes
from Step 3.

Clearly, this is a huge win in terms of performance of listing directories which have large number of directory
entries.
Next step is to hammer out the VFS patches and coreutils patch for ls to get the same benefit.
Also added a new utility called pvfs2-lsplus in src/apps/admin that uses this API.

code to coalesce db syncs.

*** empty log message ***

commit of versioning stuff to branch

onekeyval merge

removed all the keyval type stuff.  Also my prefix callback doesn't seem to be working..

mostly working onekey impl

immediate completion now turns on with: ImmediateCompletion yes option in fs config

updates to my event changes to bring them inline with trunk

merge changes from trunk since branch point into branch.  Effectively moves the branchpoint to the latest trunk.

Murali's patch to add VFS support for extended attributes.

added TROVE_NOOVERWRITE flag support for keyval writes

more doxygen work.

Moved trove prototypes into here.

- fixed trove error codes (yet another pass; this time things look
  sane)
- give trove flush and resize operations the ability to create the
  bstream they're working with if it doesn't exist instead of
  returning an error (easily triggerred on multiple servers if a small
  amount of data is written, followed by a sync -- bstreams that
  weren't yet created fail, causing the call to fail as a whole);
  pointed out by RobL
- fixed bug in (threaded) trove that did not properly reinitialize
  condition variables after the first finalize
- improvements to the storage space and collection removal code
  (rmspace)
- extensive trove cleanups and cruft removal
- check for error codes when doing server side getattr and reading
  metafile information; stop processing if an error is reached.
  pointed out by RobL
- invalidate attr cache on write_at calls (never used)
- changed pvfs2-showcoll coll_id prints from hex to decimal

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

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

- merge in as much as possible from the main tree to keep up to date

- remove redefinition of constant

- add some debugging regarding the handle reuse timing
- increase the handle reuse time to 360 seconds

- kernel updates to keep everything in sync with recent changes

This is a full merge of my pvfs2-dbpf-attr-cache-branch, so this is
the cumulative changelog (based on existing cvs messages).

- initial dbpf-attr-cache implementation and cleanups
- added all the hooks to grab configurable cacheable metadata keys
  from a config file.  re-arranged the config file by separating out
  fs specific hints into a StorageHints area.  updated genconfig to
  account for these changes.
- initial working implementation of the unified dbpf-attr and
  keyval/data pair cache.  holy cow this thing is fast... much work to
  be done still.
- initial locking added
- replaced debug level with a new DBPF_ATTRCACHE_DEBUG level
- added safe to/from cache data copies
- added write-through caching for keyval data (still need to do generic attrs)
- updated simple.conf
- allow config file to have multiple AttrCacheKeywords lines
- fix some cache parts that allow symlinks to work (i.e. be cached)
- added a verbose warning for a particular kind of configuration error
  for a user to see if it should happen
- some more robust configure checks
- more configure related changes
  disable vis build if sdl is detected, but sdl-ttf isn't
- fix broken ifdef nesting that caused compilation failure on non
  aio-threaded configurations
- safe copy of attributes (to/from, preparing for write-through impl)
- server cleanups (making way for pre-caching of a number of attrs on server
  startup since it reads them from disk during handle iterate anyway)
- update create test program to report human readable creation error
- put some quick human readable error reporting in pvfs2-client-core
- added some quickhash method we've been wanting but never had
- implemented policy to limit previously unbounded size of attr cache
- adjusted simple.conf to have some good defaults
- adjusted pvfs2-genconfig to match those defaults
- fixed some htable cleanups
- started write-through attr updates
- update changelog and version info, preparing for mainline merge
- implement write-through of dbpf-resize operation
- make sys-truncate return -PVFS_EINVAL if truncate is called on an object
  that can't be truncated
- fix error code return value of sys-truncate
- cosmetic changes to truncate test program output
- added some comments
- updated showconfig with copyright info
- updated sample configs for showconfig
- added a default handle purgatory value if a value of zero is specified
  (e.g. not specified in config file at all)
- for now, remove the cached dbpf-attr object on i/o writes
- slightly robustify the glibc aio callback detection

- added some comments
- updated showconfig with copyright info
- updated sample configs for showconfig
- added a default handle purgatory value if a value of zero is specified
  (e.g. not specified in config file at all)

added all the hooks to grab configurable cacheable metadata keys from a config
file.  re-arranged the config file by separating out fs specific hints into
a StorageHints area.  updated genconfig to account for these changes.

initial dbpf-attr-cache implementation and cleanups

iterater special value cleanups: renamed PVFS2_READDIR_START ->
PVFS_READDIR_START, defined PVFS_ITERATOR_START/END at top level types file,
redifined TROVE equivalents in terms of them, used INT32_MAX rather than
INT_MAX to reflect range of type used for position values

initial work to make the handle-mgmnt purgatory time configurable.

added a coll_id arg to trove_[open|close]_context calls.  threaded trove.
things may be badly broken now as it's on by default.  even if things appear
to work, don't be fooled.  much work is left to be done.

okay, properly gossipified trove -- seems to work now

gossipified parts of trove; added trove handle null constant

Added stubs for using contexts in trove.  None of this is working right now,
but the code *should* still work as before.  The idea is to get contexts into
the trove interface to play better with the job interface like the existing
bmi and flow interfaces.  This is the first step toward that end.

Mostly set the code up to assign handles within a range.  There are still
places where the ranges are not used, so those will be changed over as I
see them.  Also some warning removals.

Added trove support for knowing when the requested handle should be used
specifically, rather than as a range specification.  Handle mgmt doesn't
understand multiple ranges atm, so we're (poorly) faking this for now.

dumb.  missing semicolon

start defining flags for trove_collection{get,set}info

vim formatting line fixes, using pvfs2fixbadformat.pl.

Implemented and tested (for simple cases only) collection iterate.  Had to change TROVE_ITERATE_START and TROVE_ITERATE_END values.

Monster checkin:
- removed the trove "fs" files, which are no longer in use.
- added dbpf-collection.c, which keeps up with multiple collections in use
  at one time.
  - hooks in place in dbpf implementation to theoretically handle multiple
    collections; untested (works for one collection).
- added trove-create-stress.c, a stress test for object creation.
- added TROVE_SYNC flag as an option, which is handled in most calls.
- found and removed a number of problems in error handling in dbpf calls.
- created pvfs2codecheck to identify issues in the code to be cleaned up.
- eliminated a number of memory leaks in trove dbpf.
- moved flags into top of the op structure in trove.
- implemented (but did not test) dspace_verify().

Enabled use of "malloc trace" via --with-mtrace to configure.  Currently enabled in the trove initialize; we should eventually get the initialize call moved into some higher level initialize call in the library and in the server.

formatting blues.

Added vim (and emacs) formatting option comments where missing in trove subdir.

Even better job of dealing with handle iteration...this one should work for any # of dspaces.  Need to update keyval iterate functions to operate the same way.

Imported sources

Initial revision