Your understand is correct, I saw the issue happens on both 17.11 and 16.11 both
From: Andrew Rybchenko [mailto:arybche...@solarflare.com] Sent: Monday, December 10, 2018 2:57 PM To: Zhang, Qi Z <qi.z.zh...@intel.com>; Yongseok Koh <ys...@mellanox.com> Cc: dev@dpdk.org; Ivan Malov <ivan.ma...@oktetlabs.ru> Subject: Incorrectly applied ethdev: fix queue start to 17.11 Hi, Do I understand correctly that the following patch was incorrectly applied on 17.11 since changes are done in queue stop functions instead of queue start functions? If so, could you fix it, please. Also I think it makes sense to check other stable branches as well. We observe regressions because of the changeset. Andrew. commit d48890a39af7ae5c2d79dad02dd3ea3df8b6db82 Author: Qi Zhang <qi.z.zh...@intel.com><mailto:qi.z.zh...@intel.com> Date: Thu Mar 22 20:59:01 2018 +0800 ethdev: fix queue start [ upstream commit 239c9b435ad4abcac89b5d2480a0c21ce8b8288f ] Device must be started before start any queue. Fixes: 0748be2cf9a2 ("ethdev: queue start and stop") Signed-off-by: Qi Zhang <qi.z.zh...@intel.com><mailto:qi.z.zh...@intel.com> Acked-by: Konstantin Ananyev <konstantin.anan...@intel.com><mailto:konstantin.anan...@intel.com>