[dpdk-dev] running dpdk application on the same machine with other none dpdk application

[Shirley Avishour]

Perhaps by modifying the function set_cpus_allowed() which sets the kernel
threads flag with PF_NO_SETAFFINITY.
To remark it in the kernel code and to recompile the code.


On Wed, Jan 30, 2019 at 10:27 AM Shirley Avishour <shirley at imvisiontech.com>
wrote:

> Hi Rami,
> This is correct but that is because the default value of the PF_NO_SETAFFINITY
> flags does not allow to set affinity to kernel threads from user space.
> I was looking for a way to change the kernel and recompile it to be able
> to block kernel threads from running on the cpu isolated cores. (same as
> user space threads).
>
> BR,
> Shirley.
>
>
>
> On Wed, Jan 30, 2019 at 10:18 AM Rami Rosen <ramirose at gmail.com> wrote:
>
>> Hi Shirley,
>>
>> > Do you know if the PF_NO_SETAFFINITY flag can help in any way?
>>
>> AFAIK, this will not work for kernel thread.
>>
>> For example, with 4.8.13-1 kernel:
>> Display all kernel threads with
>> ps aux | grep "\["n
>>
>> (as kernel threads are enclosed in square brackets, [ ])
>> And pick one of them and try:
>> taskset -pc 7 521
>> pid 521's current affinity list: 0-15
>> taskset: failed to set pid 521's affinity: Invalid argument
>> Regards,
>> Rami Rosen
>>
>>