Hi, On Wednesday, November 28, 2018, 7:39:53 PM CET kernel@xxxxxxxxxxxxxxxx wrote: > [...] > So I am wondering: is there a good idea already how this worsted case > issue can get avoided in the first place? > > What I could come up with is the idea of: > * queuing packets in a ring buffer of a certain size > * having a separate submission thread that pushes messages onto the > network stack (essentially the short code above) > > The idea is that this thread would (hopefully) get scheduled on a different > core so that the CPU resources would get better used. Please be aware of this problem when considering multiple CPUs: https://marc.info/?l=linux-can&m=148000256801316&w=2 Best regards, Alexander -- SYS TEC electronic GmbH Am Windrad 2 08468 Heinsdorfergrund Germany Telefon : +49 (0) 3765 38600-0 Fax : +49 (0) 3765 38600-4100 Email : alexander.stein@xxxxxxxxxxxxxxxxxxxxx Website : http://www.systec-electronic.com Managing Director : Dipl.-Phys. Siegmar Schmidt Commercial registry : Amtsgericht Chemnitz, HRB 28082 USt.-Id Nr. : DE150534010 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
