diff options
author | Alex Elder <elder@inktank.com> | 2013-03-06 23:39:39 -0600 |
---|---|---|
committer | Sage Weil <sage@inktank.com> | 2013-05-01 21:16:58 -0700 |
commit | 7fe1e5e57b84eab98ff352519aa66e86dac5bf61 (patch) | |
tree | e63f60e28bdcc52c10507cf9fc9d772aa8577411 /tools | |
parent | dd236fcb65d7b6b80c408cb5f66aab55f4594284 (diff) | |
download | blackbird-op-linux-7fe1e5e57b84eab98ff352519aa66e86dac5bf61.tar.gz blackbird-op-linux-7fe1e5e57b84eab98ff352519aa66e86dac5bf61.zip |
libceph: use data cursor for message pagelist
Switch to using the message cursor for the (non-trail) outgoing
pagelist data item in a message if present.
Notes on the logic changes in out_msg_pos_next():
- only the mds client uses a ceph pagelist for message data;
- if the mds client ever uses a pagelist, it never uses a page
array (or anything else, for that matter) for data in the same
message;
- only the osd client uses the trail portion of a message data,
and when it does, it never uses any other data fields for
outgoing data in the same message; and finally
- only the rbd client uses bio message data (never pagelist).
Therefore out_msg_pos_next() can assume:
- if we're in the trail portion of a message, the message data
pagelist, data, and bio can be ignored; and
- if there is a page list, there will never be any a bio or page
array data, and vice-versa.
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions