Hi Marcin,
>
> Hi Akhil,
> I've double checked and there is no problem with linking application against
> shared libraries, because inline functions are being inlined during
> compilation
> and before linking is done. To be more specific: there is not such symbol as
> rte_ipv6_get_next_ext in ip
Hi Akhil,
I've double checked and there is no problem with linking application against
shared libraries, because inline functions are being inlined during compilation
and before linking is done. To be more specific: there is not such symbol as
rte_ipv6_get_next_ext in ipsec-secgw.o (which uses t
Hi Konstantin,
>
> Hi Akhil,
>
> >
> > Hi Marcin,
> >
> > >
> > > Introduce new function for IPv6 header extension parsing able to
> > > determine extension length and next protocol number.
> > >
> > > This function is helpful when implementing IPv6 header traversing.
> > >
> > > Signed-off-by:
Hi Akhil,
>
> Hi Marcin,
>
> >
> > Introduce new function for IPv6 header extension parsing able to
> > determine extension length and next protocol number.
> >
> > This function is helpful when implementing IPv6 header traversing.
> >
> > Signed-off-by: Marcin Smoczynski
> > ---
> > lib/lib
Hi Marcin,
>
> Introduce new function for IPv6 header extension parsing able to
> determine extension length and next protocol number.
>
> This function is helpful when implementing IPv6 header traversing.
>
> Signed-off-by: Marcin Smoczynski
> ---
> lib/librte_net/rte_ip.h | 49 +
>
> Introduce new function for IPv6 header extension parsing able to
> determine extension length and next protocol number.
>
> This function is helpful when implementing IPv6 header traversing.
>
> Signed-off-by: Marcin Smoczynski
> ---
Acked-by: Konstantin Ananyev
> 2.21.0.windows.1
6 matches
Mail list logo
