> Subject: [PATCH v3 1/5] mbuf: clarify meta data needed for Outbound Inline
>
> Clarify mbuf meta data needed for Outbound Inline processing.
> Application needs to provide mbuf.l3_len and L3 type in
> mbuf.ol_flags so that like tunnel mode using mbuf.l2_len, transport mode
&g
21/09/2022 20:21, Akhil Goyal:
> > Ping. Any thoughts on this ?
> >
> > This is just clarification of existing assumptions for Inline Outbound
> > that are being made.
> >
> >
> > On 2022-08-22 8:08 PM, Nithin Dabilpuram wrote:
> > > Clarify mbuf meta data needed for Outbound Inline processing.
> Ping. Any thoughts on this ?
>
> This is just clarification of existing assumptions for Inline Outbound
> that are being made.
>
>
> On 2022-08-22 8:08 PM, Nithin Dabilpuram wrote:
> > Clarify mbuf meta data needed for Outbound Inline processing.
> > Application needs to provide mbuf.l3_len an
Ping. Any thoughts on this ?
This is just clarification of existing assumptions for Inline Outbound
that are being made.
On 2022-08-22 8:08 PM, Nithin Dabilpuram wrote:
Clarify mbuf meta data needed for Outbound Inline processing.
Application needs to provide mbuf.l3_len and L3 type in
mbuf.
Clarify mbuf meta data needed for Outbound Inline processing.
Application needs to provide mbuf.l3_len and L3 type in
mbuf.ol_flags so that like tunnel mode using mbuf.l2_len, transport mode
can make use of l3_len and l3_type to determine perform
proper transport mode IPsec processing.
Signed-off-
5 matches
Mail list logo