From: Bharath Ravi
Hi Lee,
Martin asked for you to re-review this patch before he applies it, since
there was a small change from v3 after you acked it. The change is that
we started to protect the list_empty() verification with the spin lock
on session destruction.
For that reason, I dropped
Hello,
I am not an expert in CEPH.
However, iSCSI is the transport protocols to connect an initiator to a
target. On the client side, iSCSI traffic coming from target is broken
down and the SCSI commands are handed to the client. When writing data,
the iSCSI initiator encoded the command
Hi,
I have some questions regarding iSCSI and Ceph RBD. If I have understood
correctly, the RBD backstore module
on target side can translate SCSI IO into Ceph OSD requests. The iSCSI
target driver with rbd.ko can expose Ceph cluster
on iSCSI protocol. If correct, then that all is happening on
thanks...yes, it helped :-)
On Sunday, January 12, 2020 at 4:32:55 AM UTC+1, The Lee-Man wrote:
>
> On Jan 11, 2020, at 11:26 AM, Bobby >
> wrote:
>
>
> Hi ,
>
> Thanks for your patience regarding my questions. Because after I had dug
> (digged) very older posts, I realized
> many of the
> On Jan 24, 2020, at 3:43 AM, Vladislav Bolkhovitin wrote:
>
>
>> ...
>
> From my old iSCSI target development days, MS is fundamentally not
> friendly to multi-queue, because it requires by the iSCSI spec to
> preserve order of commands inside the session across multiple
> connections.
On 1/24/20 12:43 AM, Vladislav Bolkhovitin wrote:
>
> On 1/23/20 1:51 PM, The Lee-Man wrote:
>> On Wednesday, January 15, 2020 at 7:16:48 AM UTC-8, Bobby wrote:
>>
>>
>> Hi all,
>>
>> I have a question regarding multi-queue in iSCSI. AFAIK, *scsi-mq*
>> has been functional in
