Introduce execution domains in code and building
Only fixed to compile. Untested.
Lots of refactoring, cleanup, and fixing in the process.This log has three parts:1. What are execution domains and why we need them2. What are the API incompatibilities introduced...
relative pointers
make some field types arch-neutral
Move segment unmap() in xsegbd module.
We cannot unmap a segment in xseg_destroy(), since the segment may notbe mapped. Since it currently only affects xsegbd, move it inxsegbd_xseg_quit(), inside the xsegbd module.
Make sure to unmap the segment in xseg_destroy()
Add xops->unmap() in xseg_destroy(). If you don't unmap the segment beforecalling xops->deallocate(), xsegdev->callback and xsegdev->callarg are not setto NULL when rmmoding xsegbd, and lead to an error (or kernel panic) when trying...
Add (initial) support for X_INFO request operation
Add support for X_INFO request operation, to query information about atarget (X_INFO op support implemented in xseg-tool). Initial blockdimplementation 'returns' only the size of the target / file.
remove obsolete XSEG_{FLUSH,FUA}.
relax shared segment access precautions
The shared array of peer type names is by designappend only, therefore no locking or copying stringsis needed to access it (only pointer conversions).Append-only means that peer type names cannot be unregistered....
fix invalid shared pointer access and wrong retval
also, lock and copy string from shared segment,as a precaution.
initialization from my own repository
View revisions
Also available in: Atom