Thank you for the clarification.
On Mon, 19 Sep 2022, 10:34 pm Stephen Hemminger,
wrote:
> On Sun, 18 Sep 2022 22:05:57 +0530
> Kamaraj P wrote:
>
> > Yes. The core mask we have aligned to separate cgroup. Probably this
> might
> > be an issue here. We will change the alignment in our DPDK app
On Sun, 18 Sep 2022 22:05:57 +0530
Kamaraj P wrote:
> Yes. The core mask we have aligned to separate cgroup. Probably this might
> be an issue here. We will change the alignment in our DPDK application.
> BTW is there a way to check the cores affinity set to DPDK after
> rte_eail_init ? Do we ha
Hi Stephen,
Yes. The core mask we have aligned to separate cgroup. Probably this might
be an issue here. We will change the alignment in our DPDK application.
BTW is there a way to check the cores affinity set to DPDK after
rte_eail_init ? Do we have to use the taskset command ?
Please advise.
Th
On Fri, 16 Sep 2022 09:37:32 +0530
Kamaraj P wrote:
> Hi Team,
> Have sent a message to DPDK alias. Can you please have a look and share
> your thoughts on this ?
Top posting and nag messages just make developers angry
>
> On Thu, Sep 15, 2022 at 10:27 PM Kamaraj P wrote:
>
> > Hi Team,
> >
Hi Team,
Have sent a message to DPDK alias. Can you please have a look and share
your thoughts on this ?
Thanks,
Kamaraj
On Thu, Sep 15, 2022 at 10:27 PM Kamaraj P wrote:
> Hi Team,
>
> There are lot of discussion about below code:
> rte_panic("Cannot set affinity %d i %d threadid %d\n", ret,
Hi Team,
There are lot of discussion about below code:
rte_panic("Cannot set affinity %d i %d threadid %d\n", ret, i,
lcore_config[i].thread_id);
Is there any guildiness(or patch) from the DPDK community about avoiding
these panic messages in our DPDK application ? Even if we remove the panic
to
6 matches
Mail list logo