On Nov 18, 2014, at 3:35 PM, Lee Duncan <leeman.dun...@gmail.com> wrote:
> The following patch fixes a problem where the CPU becomes compute bound > when rediscovering targets, when there are hundreds of sessions. > > When his occurs, most of the time is spent in the function > iscsi_sysfs_for_each_session(). This function does a scandir(), > sorted alphabetically, to get a list of sessions, then scans > that list looking for a match. When there are hundreds of sesions > this can take forever. > > This patch saves the current session and then ensures that this > session sorted to the front of the list. Testing shows that > CPU usage goes from near 100% to near 0% when running cable > plug tests with hundreds of sessions. When/how is iscsi_sysfs_for_each_session getting run during this test? Is it iscsid during its relogin/eh handling or something else like a script running iscsiadm commands? -- 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 http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.