At the time it was written, upstream preferred code that could be in userspace to be implemented in userspace. So for example, dm-multipath, which was implemented around the same time as open-iscsi, had its error handler and device assembly done in userspace.
There is a engineer from Emulex working on pushing this code back to the kernel to simplify things. On 06/07/2015 07:58 AM, WangMike wrote: > Is there any reason that put error/recovery logic to a user space > application? As we can see that NFS/CIFS they all handle such thing in kernel > space. > > > ---------------------------------------- >> Date: Sat, 6 Jun 2015 12:04:42 -0500 >> From: [email protected] >> To: [email protected] >> Subject: Re: iscsistart and iscsid >> >> On 6/6/15, 7:56 AM, [email protected] wrote: >>> Hi, >>> >>> I run iscsistart in initrd to bring up all iscsi disks (include root disk). >>> After switch root, do I still need run iscsid service, considering I have >>> no need to run iscsiadm for administration operations. >>> >> >> Yes, because iscsid handles iscsi errors/recovery. >> >> -- >> 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 [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/open-iscsi. >> For more options, visit https://groups.google.com/d/optout. > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
