Ok, because error phenomena happens during the period VF reset again and again following situation will possible happen as following steps describe: step 1. DCF state has been set to on after VF has reset. step 2. A VF reset happen, kernel send an event to DCF and set STATE to pause. step 3. Before DCF receive the event, it is possible a rule creation is ongoing, then in virtual channel queue, the rule request is in front of the "re-connect", then it will be rejected. step 4.But the DCF state is not set to pause, according to previous logic error code will be EINVAL, while not EAGAIN.
In conclusion, in upper situation error code which should not be EINVAL and EAGAIN is expected. > -----Original Message----- > From: Zhang, Qi Z <qi.z.zh...@intel.com> > Sent: Tuesday, May 17, 2022 3:36 PM > To: Zhang, Peng1X <peng1x.zh...@intel.com>; Yang, Qiming > <qiming.y...@intel.com>; dev@dpdk.org > Cc: sta...@dpdk.org > Subject: RE: [PATCH v2] net/ice: fix DCF state checking mechanism > > > > > -----Original Message----- > > From: Zhang, Peng1X <peng1x.zh...@intel.com> > > Sent: Wednesday, May 11, 2022 11:50 PM > > To: Yang, Qiming <qiming.y...@intel.com>; Zhang, Qi Z > > <qi.z.zh...@intel.com>; dev@dpdk.org > > Cc: Zhang, Peng1X <peng1x.zh...@intel.com>; sta...@dpdk.org > > Subject: [PATCH v2] net/ice: fix DCF state checking mechanism > > > > From: Peng Zhang <peng1x.zh...@intel.com> > > > > DCF state previous checking mechanism can not fully detect DCF state > > whether is on or not,so PMD will report uncorrect error code in some > > cases and mislead user.Fix DCF state checking mechanism which will > > mention user resource temporarily unavailable when DCF state is not on. > > > Please describe at which situation which error code is uncorrect and which is > expected. > >
