On Thu, Feb 14, 2019 at 11:05 AM Burakov, Anatoly <anatoly.bura...@intel.com> wrote:
> On 14-Feb-19 9:53 AM, David Marchand wrote: > > > A bit more context then, if you want to clearly pin cpu resources for > > the processes on your system (let's say having virtual machines and a > > popular vswitch), I can only think of two solutions. > > Either you have something to configure your processes to have them call > > sched_setaffinity/pthread_set_affinity_np, or you use taskset to get > > them "jailed" without them caring. > > > > Before the incriminated commit, we were keeping all threads on the > > coremask that had been passed, but as Olivier said, we would end up with > > ctrl threads spanwed on core running dataplane threads as well. > > > > Now, the ctrl threads can be spawned anywhere on all & ~coremask, with > > no way to configure this. > > I considered adding a new eal option, but I think relying on the current > > cpu affinity is a better default behavior and I can't see drawbacks at > > the moment. > > OK, that makes sense. However, i feel this behavior (both old and new, > for that matter) should be better documented somewhere in the EAL docs. > > I'll see what I can add in the doc for v2. -- David Marchand
