tree 33c853319e28ed9dd20835c1f3f066be404b50a1
parent 2ac2b7a6d4976bd6b5dc0751aa77d12d48d3ac4c
author Alex Elder <elder@inktank.com> 1360865803 -0600
committer Sage Weil <sage@inktank.com> 1367468187 -0700

libceph: separate read and write data

An osd request defines information about where data to be read
should be placed as well as where data to write comes from.
Currently these are represented by common fields.

Keep information about data for writing separate from data to be
read by splitting these into data_in and data_out fields.

This is the key patch in this whole series, in that it actually
identifies which osd requests generate outgoing data and which
generate incoming data.  It's less obvious (currently) that an osd
CALL op generates both outgoing and incoming data; that's the focus
of some upcoming work.

This resolves:
    http://tracker.ceph.com/issues/4127

Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>