While I cannot speak for the upstream kernel maintainers, in the past they have rejected the RBD module for LIO and you might have similar issues wiring timestamp changes into tcp_recvmsg. Plus, in a large deployment where you have lots of initiators connecting to lots of targets, I really wonder what benefit you will receive from active/active versus just level-loading the targets and not having to deal w/ the added racy complexities. On Mon, May 14, 2018 at 6:16 AM, David Disseldorp <ddiss@xxxxxxx> wrote: > On Wed, 2 May 2018 00:36:04 +0200, David Disseldorp wrote: > >> The Ceph (v13.0.2-1974) OSD request expiry functionality is added via a >> new (likely in the completely wrong place) class="user" fn="expire_req" >> call: >> https://github.com/ddiss/ceph/commits/poc_osd_req_expiry >> >> This new class function is then invoked via an op that is prefixed to >> all kRBD OSD write requests *if* the image is mapped with a >> write_expiry_msec=X parameter: >> https://git.samba.org/?p=ddiss/linux.git;a=shortlog;h=refs/heads/poc_krbd_wreq_expiry > > Ping, did anyone else get a chance to look at this? Is there any > interest in also going in this direction for active / active > tcmu-runner support? > > Cheers, David > -- > 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 -- Jason -- 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
