Did anything ever result from this? Is there a kernel patch available that should resolve the issue? I'm considering rebuilding my server with RHEL7 since it uses Linux kernel 3.10, which I've had great luck with in the past. I would hate to lose VAAI, but I haven't had any success with LIO in the years since that was implemented, despite spending thousands of dollars on hardware and countless hours troubleshooting. Is there no testing done with ESXi connect via FC? The wiki doesn't even mention anything newer than ESX/ESXi 4... On Thu, Jan 28, 2016 at 2:28 AM, Thomas Glanzmann <thomas@xxxxxxxxxxxx> wrote: > Hello Nab, > thank you for the elaboration. I was not aware of that issue. > >> It's still unclear (to me at least) at what number of LUNs per session >> this becomes a problem for ESX, but I usually recommend users keep it in >> the half dozen range (or less) per individual TargetName >> +TargetPortalGroupTag endpoint. > > I go one step further and use one LUN per TPG. The reason for this > is that I read long time ago in the UserGuide that each TPG is > bound to one CPU on the target. Is that also still the case? By using > one LUN per TPG I spread the load equally over all available Hyper > Threads. At least this was my intention. > > Cheers, > Thomas > -- > To unsubscribe from this list: send the line "unsubscribe target-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
