On 13-12-2017 16:34, Sage Weil wrote:
We had a great chat yesterday with Avi Kivity @ Scylla about seastar in ceph, and were talking about where to start... One candidate was to carve off the entire messenger and reimplement using seastar futures/promises.
I don't think it's a good idea to start with the messenger since we are currently making a lot of changes to implement the new V2 protocol.
Another thought that is somewhat trivial but probably necessary and smallish is the log/ framework. This might be a good test case for the legacy <-> seastar communications infrastructure. It's all one-way, which simplifies things a bit, and the implementation should be pretty straightforward? I know we can't rely on the current debug stuff for tracing/instrumentation, but I don't think teh need for a debug log is going to go away. Another question is how the logger/perfcounters will need to change in a seastar world. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
-- Ricardo Dias Senior Software Engineer - Storage Team SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
