From 466f0d46d242aea1a598f5a9922528aa38d1653b Mon Sep 17 00:00:00 2001 From: Jon Loeliger Date: Thu, 9 Feb 2017 12:17:50 -0600 Subject: Augment IP_DETAILS, IP_ADDRESS_DETAILS with a few context fields. When handling the IP_DETAILS and IP_ADDRESS_DETAILS replies, it is almost certainly going to require having both the is_ipv6 and sw_if_index context to handle them properly. Placing these values in an essentially global location as the current VAT does isn't thread-safe. Fruthermore, rather than forcing every API user to hoop-jump to establish these context values, simply provide them in their DETAILS reply messages. Change-Id: I6a9e0cb16ecdbf87fca8fc5c7663e98d3a53c26c Signed-off-by: Jon Loeliger --- src/vnet/ip/ip.api | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/vnet/ip/ip.api') diff --git a/src/vnet/ip/ip.api b/src/vnet/ip/ip.api index 65f6e7a7..0a4a9c97 100644 --- a/src/vnet/ip/ip.api +++ b/src/vnet/ip/ip.api @@ -436,6 +436,8 @@ define ip_address_details u32 context; u8 ip[16]; u8 prefix_length; + u32 sw_if_index; + u8 is_ipv6; }; define ip_address_dump @@ -450,6 +452,7 @@ define ip_details { u32 sw_if_index; u32 context; + u8 is_ipv6; }; define ip_dump -- cgit 1.2.3-korg