On 01/08/15 14:45, Sagi Grimberg wrote:
Actually I started with that approach, but the independent connections
under a single session (I-T-Nexus) violates the command ordering
requirement. Plus, such a solution is specific to iSER...
Which command ordering requirement are you referring to ? The Linux
storage stack does not guarantee that block layer or SCSI commands will
be processed in the same order as these commands have been submitted.
However, it might be interesting to have a look at virtscsi_pick_vq(). I
think the purpose of that function is to keep queueing to the same hwq
as long as any commands are being executed. This approach avoids that if
an application is migrated by the scheduler from one CPU to another that
commands get reordered due to have been submitted to different hwq's. I
don't think we already have something similar in blk-mq but this is
something that could be discussed further.
(we might want to leave something for LSF ;)).
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.