On Thu, Mar 16, 2017 at 9:25 PM, 许雪寒 wrote:
> Hi, Gregory.
>
> On the other hand, I checked the fix 63e44e32974c9bae17bb1bfd4261dcb024ad845c
> should be the one that we need. However, I notice that this fix has only been
> backported down to v11.0.0, can we simply apply it to our Hammer
> versi
Hi, Gregory.
On the other hand, I checked the fix 63e44e32974c9bae17bb1bfd4261dcb024ad845c
should be the one that we need. However, I notice that this fix has only been
backported down to v11.0.0, can we simply apply it to our Hammer
version(0.94.5)?
-邮件原件-
发件人: 许雪寒
发送时间: 2017年3月17日 1
I got it. Thanks very much:-)
发件人: Gregory Farnum [mailto:gfar...@redhat.com]
发送时间: 2017年3月17日 2:10
收件人: 许雪寒
抄送: ceph-users@lists.ceph.com; jiajia zhong
主题: Re: 答复: [ceph-users] 答复: 答复: Pipe "deadlock" in Hammer, 0.94.5
On Thu, Mar 16, 2017 at 3:36 AM 许雪寒 wrote:
Hi, Gregory, is it possible to
Hi, Gregory, is it possible to unlock Connection::lock in Pipe::read_message
before tcp_read_nonblocking is called? I checked the code again, it seems that
the code in tcp_read_nonblocking doesn't need to be locked by Connection::lock.
-邮件原件-
发件人: Gregory Farnum [mailto:gfar...@redhat.co
