summaryrefslogtreecommitdiffstats
path: root/Documentation/misc-devices/lis3lv02d
diff options
context:
space:
mode:
authorAlex Elder <elder@inktank.com>2013-03-11 23:34:23 -0500
committerSage Weil <sage@inktank.com>2013-05-01 21:17:30 -0700
commit4c59b4a278f9b7a418ad8af933fd7b341df64393 (patch)
tree8f42d880e2ed3fb97c64ea293b42ff08f891537a /Documentation/misc-devices/lis3lv02d
parent686be20875db63c6103573565c63db20153ee6e1 (diff)
downloadtalos-op-linux-4c59b4a278f9b7a418ad8af933fd7b341df64393.tar.gz
talos-op-linux-4c59b4a278f9b7a418ad8af933fd7b341df64393.zip
libceph: collapse all data items into one
It turns out that only one of the data item types is ever used at any one time in a single message (currently). - A page array is used by the osd client (on behalf of the file system) and by rbd. Only one osd op (and therefore at most one data item) is ever used at a time by rbd. And the only time the file system sends two, the second op contains no data. - A bio is only used by the rbd client (and again, only one data item per message) - A page list is used by the file system and by rbd for outgoing data, but only one op (and one data item) at a time. We can therefore collapse all three of our data item fields into a single field "data", and depend on the messenger code to properly handle it based on its type. This allows us to eliminate quite a bit of duplicated code. This is related to: http://tracker.ceph.com/issues/4429 Signed-off-by: Alex Elder <elder@inktank.com> Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Diffstat (limited to 'Documentation/misc-devices/lis3lv02d')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud