Re: Using all 24-bits of the ISID
On 05/13/2016 11:58 AM, The Lee-Man wrote: > When we made the most recent changes to open-iscsi: > > "make use of all 24 bits of ISID qualifier space" > > we agreed it would be a "good thing" to modify the kernel > to use the "id" routines instead of an atomic int. > > I created a set of patches and submitted them, and they > got comments, but the current version has sat for a month > without comment. Are you talking about the ida patches? I gave you comments, but never got a response. I thought it could cause a regression. It probably got messed up in the threading because I dropped linux-scsi and lkml since it was userspace stuff. Will bounce it to you offlist. > > I'd really like to either get these changes into the kernel > if we want them there. > > Can anyone on the list review them, please, if they get a chance? > > On LKML or linux-scsi, the subject is: > > "Re: [PATCHv3 0/2] target: make location of /var/targets configurable" > You mean the "Use ida_simple for SCSI iSCSI transport session id" thread right? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Using all 24-bits of the ISID
When we made the most recent changes to open-iscsi: "make use of all 24 bits of ISID qualifier space" we agreed it would be a "good thing" to modify the kernel to use the "id" routines instead of an atomic int. I created a set of patches and submitted them, and they got comments, but the current version has sat for a month without comment. I'd really like to either get these changes into the kernel if we want them there. Can anyone on the list review them, please, if they get a chance? On LKML or linux-scsi, the subject is: "Re: [PATCHv3 0/2] target: make location of /var/targets configurable" Thank you. -- Lee Duncan -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Question: Where are scsi commands encapsulated?
Hi, I am recently looking into the process of iSCSI initiator. I wonder where the source codes are that receive the scsi commands and encapsulate them into iscsi format. I have walked through the interaction between iscsiadm and iscsid, but I did find that. I thought it may be written in qtask structure, but it seems the payload_len is never set within the code. Could anyone help answer this question? Thanks. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
open-iscsi Ping timeout error.
Hi everyone: I create a target using fileio as the backend storage on ARM64 server. The initiator reported some errors showed bellow while perform iozone test. [178444.145679] connection14:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4339462894, last ping 4339464146, now 4339465400 [178444.145706] connection14:0: detected conn error (1011) [178469.674313] connection14:0: detected conn error (1020) [178504.420979] connection14:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4339477953, last ping 4339479204, now 4339480456 [178504.421001] connection14:0: detected conn error (1011) [178532.064262] connection14:0: detected conn error (1020) [178564.584087] connection14:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4339492980, last ping 4339494232, now 4339495484 .. I try to trace the function call of target iscsi. Then, I found the receiving thread of target iscsi blocked at fd_execute_sync_cache -> vfs_fsync_range. Further, vfs_fsync_range may takes more than 10 seconds to return,while initiator Ping timeout would happened after 5 seconds. vfs_fsync_range was call with the form vfs_fsync_range(fd_dev->fd_file, 0, LLONG_MAX, 1) every times which means sync all device cache. So, is this a bug? How does Initiator send sync_cache scsi command? Does it need to sync all device cache at once? Any reply would be thankful. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
