[Top][All Lists]

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

[lwip-devel] [task #14724] thread safe ARP cache APIs

From: Joel Cunningham
Subject: [lwip-devel] [task #14724] thread safe ARP cache APIs
Date: Wed, 15 Nov 2017 17:42:02 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0

Follow-up Comment #9, task #14724 (project lwip):

> Sounds like this is missing then? Netif index is really a level above
netifapi, isn't it?

I should clarify my comment of "no way to go from interface name/index to
struct netif", I can write code that calls LOCK_TCPIP_CORE() and then calls
netif_find().  What I meant was that its an architecture layering violation
for network application to be directly interacting with struct netif.

To me, the netifapi APIs are mainly link level operations that require a
struct netif pointer. The one exception is the recent additions of:

err_t netifapi_netif_name_to_index(const char *name, u8_t *index);
err_t netifapi_netif_index_to_name(u8_t index, char *name);

Which are meant to be used by applications.  So my thought would be if the ARP
APIs are intended to be used by applications (as opposed to link-layer
management code), then they should take index


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]