2016-09-02 17:53, Bruce Richardson: > On Thu, Sep 01, 2016 at 01:31:47AM +0000, Jianfeng Tan wrote:
It would help the discussion to have a problem statement here. > > This patch uses pthread_getaffinity_np() to narrow down detected > > cores before parsing coremask (-c), corelist (-l), and coremap > > (--lcores). > > > > The purpose of this patch is to leave out these core related options > > when DPDK applications are deployed under container env, so that > > users only specify core restriction as starting the instance. > > > > Note: previously, some users are using isolated CPUs, which could > > be excluded by default. Please add commands like taskset to use > > those cores. > > > > Test example: > > $ taskset 0xc0000 ./examples/helloworld/build/helloworld -m 1024 > > > > So, to be clear, does this patch mean that DPDK cannot use isolated cores > any more unless you explicitly run the app using taskset? > Is so, NAK, since isolating cores has been part of standard DPDK setup since > the first versions, and I don't believe that we should break that behaviour. So how could we help the container use-case? Any suggestions?
