[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] input function for netif_add(), tcpip_input or ip_input
From: |
kuwa |
Subject: |
Re: [lwip-users] input function for netif_add(), tcpip_input or ip_input? |
Date: |
Thu, 18 Mar 2004 12:42:11 +0900 (LMT) |
Hi,
From: address@hidden
Subject: [lwip-users] input function for netif_add(), tcpip_input or ip_input?
Date: Wed, 17 Mar 2004 18:17:50 -0800
> In most of the porting cases, the netif_add function seems to like use
> tcpip_input as the last argument, would it be more reasonable to use
> ip_input instead? As a matter of fact, using tcpip_input seems to slow
> down my ping a lot, while ip_input maintains the same time delay as what
> you normally would see at any unix machine. I would like to hear what is
> your opinion. Thanks.
>
> Shawn
I guess ip_input() is not multi-threaded safe to input packet to
lwIP's IP layer. While tcpip_input() is safe.
So, if you would pass incoming packet to TCP/IP task (tcpip_thread()
in tcpip.c) from the other task, I think you had better call tcpip_input().
--
Shuji KUWAHARA