add support for larger than 1 segment requests + xseg_signaling.
xsegbd: Don't destroy the segment, if it exists.
Allow disksize override with sector_size parameter.
Allow a non-zero sector_size module parameter to override the disksize returned by xsegbd_get_size()
Minor fixes in xsegbd_get_size().
Remove the useless prep_wait() and cancel_wait() calls in xsegbd_get_size() andadd some comments to document its behavior.
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.
Refactor cmd_info() code in xseg-tool.
Refactor cmd_info code in xseg-tool. Use cmd_wait to get the response.
Make xsegbd query peer for disk size(using X_INFO)
xsegbd will now send an X_INFO request to learn the size of the disk it'smapping, instead of using the sector_size parameter at module load time.
Currently, xsegbd allocates its own segment, and thus it must wait until blockd...
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 race condition on xseg_request state
make blockd loop over pending ios.
remove close with negative file descriptor
Merge branch 'philfix'
initialize lock in xq initialization.
remove obsolete XSEG_{FLUSH,FUA}.
initial commit of sosd
fix buffer handling on incomplete/resubmitted reqs
fix log_io printing beyond end-of-string garbage
Add pthread to linked libraries
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.
relax redundant shared access precautions
Shared access to the shared array of peer type nameswas designed to be safe without locking or copyingbecause the peer type name array is append only,i.e. no peer type names can be unregistered.
Unregistering introduces many other problems...
fix invalid pointer access to shared segment.
Also, add locking and copying shared data, for safety.
initialization from my own repository
« Previous 1 ... 88 89 90 (2226-2250/2250) | Per page: 25, 50, 100
Also available in: Atom