[...] >> >> The structure I used previously which looks like your prototype I think, >> >> (https://github.com/jrfastab/rocker-net-next/blob/master/include/uapi/linux/if_flow.h) >> >> * [NFL_TABLE_IDENTIFIER_TYPE] >> * [NFL_TABLE_IDENTIFIER] >> * [NFL_TABLE_TABLES] >> * [NFL_TABLE] >> * [NFL_TABLE_ATTR_NAME] >> * [NFL_TABLE_ATTR_UID] >> * [NFL_TABLE_ATTR_SOURCE] >> * [NFL_TABLE_ATTR_APPLY] >> * [NFL_TABLE_ATTR_SIZE] >> * [NFL_TABLE_ATTR_MATCHES] >> * [NFL_FIELD_REF] >> * [NFL_FIELD_REF_INSTANCE] >> * [NFL_FIELD_REF_HEADER] >> * [NFL_FIELD_REF_FIELD] >> * [NFL_FIELD_REF_MASK] >> * [NFL_FIELD_REF_TYPE] >> * [...] >> * [NFL_TABLE_ATTR_ACTIONS] >> * [NFL_ACTION_ATTR_UID] >> * [...] >> * [NFL_TABLE] >> * [...] >> * >> >> This is well-typed per Dave's comment. And because its Netlink based it >> can be easily extended as needed. The above gives basic information on >> the table. Sure it could stand to have some other entries in it but I >> never needed them for my capabilities/resource discovery. We could argue >> about removing some if they are too specific to my use cases. > > I guess you are talking about read-only interface right? >
Correct. read-only. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
