> > > > We are using this flag to allow application to choose between WFE > > > > and > > non- > WFE code path. > The non-WFE path performs slightly better. > > > Is it correct if I assume that this flag is not used to indicate the > > availability > > > > > > > > We are using this flag to allow application to choose between WFE > > > and non- WFE code path. > > > The non-WFE path performs slightly better. > > > > > > > Is it correct if I assume that this flag is not used to indicate the > > availability of WFE instruction in any of your platforms? > > If so, then its usage is to choose between WFE and non-WFE > > implementations for performance reasons. > > > > Yes, its purely for performance reasons. >
So, in that sense I don't mind keeping the name RTE_ARM_USE_WFE for the purpose of using WFE instruction on a code path based on power/performance bias. This has been the case with rte_wait_until_equal_N functions as well. If the name RTE_ARM_USE_WFE is confusing, please suggest a better name. We should also document the intended use of this flag.
