[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE : RE : RE : [lwip-users] Timers & lwip tasks (amultithreadquestionwit
From: |
Frédéric BERNON |
Subject: |
RE : RE : RE : [lwip-users] Timers & lwip tasks (amultithreadquestionwithLwIP) |
Date: |
Thu, 1 Mar 2007 09:13:51 +0100 |
Hi,
Yes, this is what I wanted to propose (but my english is not very clear) :
"More, the task receiving packets call etharp_ip_input if ETHARP_TRUST_IP_MAC
is defined (and it's always call etharp_arp_input for ARP packets - I think
that most of the code in "ethernetif_input" would have to be moved in the
"netif->input")."
====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hidden
Web Site : http://www.hymatom.fr
====================================
P Avant d'imprimer, penser à l'environnement
-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Goldschmidt Simon
Envoyé : jeudi 1 mars 2007 08:00
À : Mailing list for lwIP users
Objet : RE: RE : RE : [lwip-users] Timers & lwip tasks
(amultithreadquestionwithLwIP)
Hi,
> So, in a multithread environment with upper layers, I think
> it's a good to define ETHARP_TRUST_IP_MAC to 0, and to
> initialize the arp_timer in the tcpip_thread context (which
> can handle "timeouts") to reduce this kind of problem, like this :
That alone won't help, since etharp_arp_input() is called from network driver
context if ARP packets are received!
My solution to that problem was to pass all received packets including ARP to
the tcpip-thread which does the processing of IP- AND ARP-packets. This way,
all access to the ARP layer is done in tcpip-thread context.
Simon
_______________________________________________
lwip-users mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/lwip-users
Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- RE : RE : RE : [lwip-users] Timers & lwip tasks (amultithreadquestionwithLwIP),
Frédéric BERNON <=