Hi Marcin, > > Thank you Marcin, It shows that haproxy is waiting for an event on all those > fds because a crypto jobs were launched on the engine > and we can't free the session until the end of this job (it would result in a > segfault). > > So the processes are stucked, unable to free the session because the engine > doesn't signal the end of those job via the async fd. > > I didn't reproduce this issue on QAT 1.5 so I will try to discuss it with > intel guys to known why there is this behavior change in the v1.7 > and what we can do. > > R, > Emeric >
Just to known that I'm waiting for the feedback of intel's team and I will receive QAT 1.7 compliant hardware soon to make some tests here. R, Emeric
