On 09/14/2010 02:46 AM, Masayuki Ohtake wrote: >>>> - implement NAPI >>> Since Topcliff CAN HW register has only single rx buffer, >>> I think NAPI is unnecessary. > >> Doesn't matter. Please try to implement it. > > Our CAN driver must pull received data from CAN-HW rx buffer as fast as it can > so that the received data is not over-written by next received data. > In case of implemented with NAPI, > since NAPI has time-lagging after receiving first packet, > probability of over-written(discarded) buffer is to be high. > Thus, for our CAN HW, we should NOT implement with NAPI but normal "netif_rx".
Okay, point taken. Regarding the one and only rx buffer. Is it a driver or a hardware limitation? BTW: Are the datasheets of this CAN core available somewhere? cheers Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
