[RFC v3] c_can: improve latency and avoid packet loss

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: linux-can@xxxxxxxxxxxxxxx
Subject: [RFC v3] c_can: improve latency and avoid packet loss
From: Kurt Van Dijck <dev.kurt@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 17 Dec 2019 16:23:23 +0100
In-reply-to: <c0272077-c3c1-f106-ef51-fee546368ba6@pengutronix.de>
References: <c0272077-c3c1-f106-ef51-fee546368ba6@pengutronix.de>

Hey,

V3 is the 2nd attempt to omit KConfig values.
patches 1..8 are still identical.

I changed the order of 9,10,11 patches since V2
so that I never need any KConfig values.

Still open for remarks.

Kurt

Follow-Ups:
- Re: [RFC v3] c_can: improve latency and avoid packet loss
  - From: Elenita Hinds
- [PATCH 11/11] can: c_can: increase RX queue, TX queue fixed to 8
  - From: Kurt Van Dijck
- [PATCH 10/11] can: c_can: support 64 message objects for D_CAN
  - From: Kurt Van Dijck
- [PATCH 09/11] can: c_can: runtime message object divisions
  - From: Kurt Van Dijck

References:
- Re: [RFC] c_can: improve latency and avoid packet loss
  - From: Marc Kleine-Budde

Prev by Date: Re: [PATCH 09/11] can: c_can: support 64 message objects for D_CAN
Next by Date: [PATCH 09/11] can: c_can: runtime message object divisions
Previous by thread: [PATCH 10/11] can: c_can: message object division not hardcoded
Next by thread: [PATCH 09/11] can: c_can: runtime message object divisions
Index(es):
- Date
- Thread

[Index of Archives] [Automotive Discussions] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [CAN Bus]

Powered by Linux